Can my team share one Zesty.io connection?

Yes. One person connects Zesty.io in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who asked for which Zesty.io instance or user list.

Application Development

Zesty.io MCP connector

The Zesty.io connector lets Claude, ChatGPT, Cursor, 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.

Connect on Elaichi How to connect

How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
One address. https://api.elaichi.ai/mcp, the same for every user.
Their own access. An agent never gets more than the person it acts for.

5 tools

How to connect

How to connect Zesty.io to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Zesty.io once

Open Connections, choose Add connection, and pick Zesty.io.
Optionally set Share with to give a team access, then press Connect.
Paste a Zesty.io API key. One person generates a token in Zesty.io and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

zesty.io

All categories

Zesty.io

Apache Airflow

Apify

Boomi

Browserbase

Caspio

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

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 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 today. 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.

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.

Connect Zesty.io on Elaichi See pricing

Use cases

What teams do with Zesty.io through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

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.”

See all 5 Zesty.io tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Zesty.io, by what to check
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	$15 per user per month.	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.

AI tools

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.

See it in Elaichi

What connecting Zesty.io gets you

6 screens from the product, each doing one job for your Zesty.io account.

The agent

Ask about Zesty.io instances in plain language.

The agent answers from live Zesty.io instances, users and roles.

instances
users
roles
memberships

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Zesty.io.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

5 Zesty.io tools are cataloged and callable.

Instance and user methods are listed and ready, with no custom code written.

List all Zesty.io instances
Get single Zesty.io instance by ID
List all Zesty.io instance users
List all Zesty.io instance users with roles

ElaichiTools

Tool	Action	Description
List all Zesty.io instances	List	List all instances a user has access to in Zesty. Returns fields such as ZUID (unique identifier), name, domain, createdAt, updatedAt, blueprintZUID, screenshotURL, and other metadata for each instance.
Get single Zesty.io instance by ID	Get	Get a specific instance in Zesty.io by id (ZUID). Returns ZUID, name, domain, createdAt, updatedAt, and screenshotURL fields providing key instance details.
List all Zesty.io instance users	List	List all users for a specific instance in Zesty.io. Requires instance_zuid. Returns each user's ZUID, email, firstName, lastName, role, and timestamps for creation and updates.
List all Zesty.io instance users with roles	List	Get all users of a specific instance in Zesty.io using instance_zuid. Returns each user's details including ZUID, email, name, and their associated Role with its permissions and metadata.
List all Zesty.io user instances	List	Get user-instances for a specific user in Zesty.io using user_zuid. Returns instance details including name, ZUID, domain, blueprintZUID, createdAt, and updatedAt fields in the response.

Toolboxes

Each team gets its own Zesty.io toolbox.

Toolboxes are scoped per team, so Web and Support see different Zesty.io tools.

Web
Engineering
Marketing
Support

ElaichiToolboxes

Name	Source template	Tools	Created
Web toolbox Zesty.io · instances and content models	Zesty.io starter	18	Mar 4, 2026
Engineering toolbox Zesty.io · instance configuration	—	9	Mar 2, 2026
Marketing toolbox Zesty.io · campaign site instances	—	24	Feb 27, 2026
Support toolbox Zesty.io · instance users and access questions	Zesty.io starter	6	Feb 19, 2026
IT and Security toolbox Zesty.io · roles and instance memberships	—	31	Jan 30, 2026
Client Services toolbox Zesty.io · per client instances	—	12	Jan 22, 2026

Shared connections

Teammates use Zesty.io without seeing credentials.

The connections table shows who connected each account and how widely it is shared.

Web Platform
Marketing Sites
Client Instances
Engineering Sandbox

ElaichiConnections

Connection	Scope	Status	Access
ZE Zesty.io (Web Platform) Connected by Emily Carter	Personal	• Active	1 team · 6 members
ZE Zesty.io (Marketing Sites) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
ZE Zesty.io (Client Instances) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
ZE Zesty.io (Engineering Sandbox) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
ZE Zesty.io (Support Desk) Connected by Ryan Hayes	Personal	• Active	Not shared
ZE Zesty.io (Security Review) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every Zesty.io call is on the record.

When, who, what happened, type and resource, in an append-only log.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	Zesty.io Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Zesty.io Instances Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Zesty.io Instances List	Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule runs the Zesty.io digest.

Six steps fetch instances, group them, draft a digest, get approval, then post back.

Zesty.io digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

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 Michael Brennan

Approve Deny
Post the digest

Zesty.io

Queued

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.

Zesty.io health

Refreshed 4 minutes ago · every 15 minutes · from the instances collection

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

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, 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 blocked action is never shown to the AI client, so no prompt can reach it, for example if you want to hide the list of users with roles from a particular team.

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, 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect Zesty.io Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.