Zesty.io MCP connector
The Zesty.io connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client look up your Zesty.io instances, see who has access to each one and what role they hold, with every request tied to the person who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Which Zesty.io instances do I have access to?
Working in Zesty.io with Elaichi
-
List all Zesty.io instances
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Zesty.io to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Zesty.io 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.
Zesty.io 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.
Zesty.io 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.
Zesty.io 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.
Zesty.io 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 Zesty.io 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 Zesty.io through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Zesty.io is logged.
-
Marketing
See which Zesty.io instances you own
Ask for a list of every Zesty.io instance your team runs, with names and IDs, before planning a site refresh or a new campaign microsite.
-
Web
Pull up one instance's details fast
Give the instance ID and get back its details in seconds, without opening the Zesty.io manager and clicking through the accounts view.
-
IT
Check who has access to a site
List every user on a Zesty.io instance ahead of a handover or a vendor change, so nobody is surprised by an unfamiliar name.
-
Security
Review roles across every Zesty.io instance
Ask which users hold owner or admin roles on each instance, then flag anyone whose role is broader than their job needs.
-
Operations
Map a person to their instances
When someone moves teams or leaves, list every Zesty.io instance they belong to so offboarding covers all of them.
-
Agency
Audit client instances in one pass
Agencies running several client sites can ask for all instances and their users at once, and turn the answer into a quarterly access report.
Try asking
- “Which Zesty.io instances do I have access to?”
- “List all users and roles on our marketing instance.”
- “Show every instance where Priya holds an admin role.”
What connecting Zesty.io gets you
6 screens from Elaichi, each doing one job for your Zesty.io account.
Ask Elaichi to work across your apps.
Which Zesty.io instances do I have access to?
List all users and roles on our marketing instance.
Show every instance where Priya holds an admin role.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Zesty.io instances in plain language.
The agent answers from live Zesty.io instances, users and roles.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Zesty.io.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
5 Zesty.io tools are cataloged and callable.
Instance and user methods are listed and ready, with no custom code written.
ElaichiToolboxesToolboxes
Each team gets its own Zesty.io toolbox.
Toolboxes are scoped per team, so Web and Support see different Zesty.io tools.
ElaichiConnectionsShared connections
Teammates use Zesty.io without seeing credentials.
The connections table shows who connected each account and how widely it is shared.
ElaichiAudit logAudit log
Every Zesty.io call is on the record.
When, who, what happened, type and resource, in an append-only log.
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.
Zesty.io digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch instances
Zesty.io
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
Zesty.io
Queued
Automations
A schedule runs the Zesty.io digest.
Six steps fetch instances, group them, draft a digest, get approval, then post back.
Zesty.io health
Refreshed 4 minutes ago · every 15 minutes · from the instances collection
Instances
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Instances created
Last 14 days
By team
Share of activity
Web Platform 34%
Marketing Sites 27%
Client Instances 21%
Engineering Sandbox 18%
Collections and dashboards
Zesty.io instance health, computed on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Zesty.io
All three can connect Zesty.io 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 Zesty.io tools | Allow or restrict single Zesty.io 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 Zesty.io 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.
Zesty.io tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zesty.io, 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 Zesty.io to Claude?
Connect Zesty.io in Elaichi by pasting a Zesty.io API key when prompted. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Zesty.io instances appear in Claude.
Does Zesty.io work with ChatGPT and Cursor as well as Claude?
Yes. Once Zesty.io 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 Zesty.io once and every client picks it up.
What can an AI agent actually do with my Zesty.io data?
With this connector an agent can list your Zesty.io instances, pull up one instance by its ID, list the users on an instance, show which role each of those users holds, and list every instance a given user belongs to. It is a read-only view of instances and access, useful for access reviews, handovers, and offboarding checks.
Does connecting Zesty.io give the AI access to every instance?
No. Every request runs as the person who signed in, so the AI sees only the Zesty.io instances and users that person's API key can already reach. Elaichi can narrow that further with restrictions, and it never widens what Zesty.io itself allows.
Can I stop an agent from changing or deleting things in Zesty.io?
This Zesty.io connector only reads instances, users, and roles, so it cannot change or delete anything. On top of that, Elaichi restrictions work per action, and a restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Zesty.io connection when someone leaves?
Offboarding a person in Elaichi ends their access to Zesty.io through every client at once. If they connected a shared Zesty.io connection, it keeps working for everyone else on the team. Disconnecting Zesty.io once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.
Does the Zesty.io MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Zesty.io 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 Zesty.io?
Yes. Both let Claude, ChatGPT or Cursor use Zesty.io. 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 Zesty.io call.
How is Elaichi different from Composio for Zesty.io?
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 Zesty.io: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Zesty.io 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