Tavio MCP connector
The Tavio connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and other AI clients work with your Tavio workflows, environments, configs, solutions, users, and customers, each request running as the signed-in person and recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
List all Tavio environments and who owns each one.
Working in Tavio with Elaichi
-
List all Tavio me
-
List all Tavio users
-
Get single Tavio user by ID
How to connect Tavio to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Tavio MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Tavio MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Tavio MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Tavio MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Tavio MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Tavio to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Tavio through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Tavio is logged.
-
Operations
Check which workflows are live before a release
Ask for the full list of Tavio workflows and pull up any one by name to confirm what it does and which environment it runs in before you change anything.
-
IT
Add a new hire to Tavio in one step
Create the Tavio user, confirm their details, and update their record later when their role changes, all from the chat window where you already work.
-
Customer success
Set up a new customer on their first day
Create the customer in Tavio, connect their environment, and confirm the setup is in place while you are still on the kickoff call.
-
Implementation
Fix a config without opening the console
Look up the config behind a solution, compare it with what the customer asked for, and update the values that are wrong.
-
Support
Find out why a workflow stopped running
Pull up the workflow and its config, read them together, and tell the customer what changed rather than guessing.
-
Operations
Retire environments nobody uses anymore
List every Tavio environment, spot the ones from finished pilots or departed customers, and remove them so the account stays clean.
Try asking
- “List all Tavio environments and who owns each one.”
- “Which Tavio users were added to production this month?”
- “Show Tavio customers with no solutions connected yet.”
What connecting Tavio gets you
6 screens from Elaichi, each doing one job for your Tavio account.
Ask Elaichi to work across your apps.
List all Tavio environments and who owns each one.
Which Tavio users were added to production this month?
Show Tavio customers with no solutions connected yet.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Tavio users, get real answers.
Plain language questions answered from live Tavio users, environments and solutions.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Tavio.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
All 30 Tavio tools are ready now.
Users, environments, connections, customers and solutions covered without writing custom code.
Toolboxes
Every team gets its own Tavio toolbox.
Curate one toolbox per team so each sees only the Tavio tools it needs.
Shared connections
Teammates use Tavio without holding credentials.
Each connection shows who connected it and which teams and members share it.
Audit log
Answer who changed which Tavio environment.
Append-only log of when, who, what happened, type and Tavio resource touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Tavio digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Tavio
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Tavio
Queued
Automations
A schedule fires, Tavio work gets done.
Six steps fetch Tavio environments, group them, draft a digest, await approval, post back.
Tavio health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Environments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Platform 34%
Support EMEA 27%
Security 21%
Solutions 18%
Collections and dashboards
Tavio numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Tavio
All three can connect Tavio to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Tavio tools | Allow or restrict single Tavio tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Tavio call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Tavio tools for your AI agents
30 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tavio, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Tavio to Claude?
Connect Tavio in Elaichi first: Tavio uses an API key, so you paste the key from your Tavio account into Elaichi and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Tavio appears in Claude.
Does Tavio work with ChatGPT and Cursor as well as Claude?
Yes. Once Tavio is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Tavio once and every client you use picks it up.
What can an AI agent actually do with my Tavio data?
With Tavio connected, an agent can list and read your workflows, environments, configs, solutions, and users, and it can create and update workflows, configs, and users, create customers, and connect environments. In practice that means asking which workflows exist for a customer, fixing a config value, adding a teammate, or removing an unused environment, all in plain language. It can only do what the Tavio connector offers, nothing beyond it.
Does connecting Tavio give the AI access to every environment and workflow?
No. Every request to Tavio runs as the person who signed in, so the AI can only see the environments, workflows, and configs that person's Tavio access already allows. Elaichi can narrow that further, for example to read-only or to a subset of actions, but it can never widen what Tavio itself permits.
Can I stop an agent from deleting or changing things in Tavio?
Yes. Restrictions in Elaichi work per action, so you can allow reading Tavio workflows and configs while restricting updates, or restrict deleting users, environments, and workflows altogether. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to a Tavio connection when someone leaves?
Offboarding a person in Elaichi ends their access to Tavio through every AI client at once, with no key to rotate. If they shared a Tavio connection with a team, that connection keeps working for everyone else. If you ever want Tavio gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Tavio MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tavio is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Tavio?
Yes. Both let Claude, ChatGPT or Cursor use Tavio. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Tavio call.
How is Elaichi different from Composio for Tavio?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Tavio: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tavio in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot