Zite MCP connector
Connect Zite to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can query and edit Zite databases, build and publish Zite apps, and manage workspaces and member roles, each person signed in as themselves.
-
How it connects. Connects over OAuth. 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.
How to connect
How to connect Zite to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Zite once
-
Open Connections, choose Add connection, and pick Zite.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Zite. Zite's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
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.
Zite 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.
Zite 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.
Zite 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 Zite 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.
Use cases
What teams do with Zite through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Keep an internal tracker current without opening it
Ask for the rows in a Zite database that changed this week, then have the agent fix a status or add a missing entry while you are still in the conversation.
-
Product
Turn a spec into a working Zite app
Describe the screens and fields you need and have the agent build the app in Zite, then publish it once you have reviewed what it made.
-
Sales
Log a lead into the right database
After a call, tell the agent who you spoke to and what they want, and it adds the row to your Zite leads database with the fields filled in.
-
Support
Find every open request for one customer
Ask which rows in the Zite requests database belong to a customer and are still open, and get the list with owners and dates in one answer.
-
IT
Manage who is in each Zite workspace
Add a new hire to the right Zite workspace with the right role, or list everyone who still has editor access before a quarterly review.
-
HR
Run onboarding from a Zite app
Have the agent add each new starter to the onboarding database, check which steps are still unticked, and publish an updated version of the onboarding app.
Try asking
- “Show me every row in the customer requests database updated this week.”
- “Add a new member to the Operations workspace as an editor.”
- “Which Zite apps are published and who owns each one?”
Compare
Elaichi vs Zapier MCP vs Composio for Zite
All three can connect Zite 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 Zite tools | Allow or restrict single Zite 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 Zite 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.
See it in Elaichi
What connecting Zite gets you
5 screens from the product, each doing one job for your Zite account.
The agent
Ask Zite a question, get a live answer.
Query Zite databases, update rows and check app status in plain language.
- databases
- apps
- workspaces
- members
Ask Elaichi to work across your apps.
Show me every row in the customer requests database updated this week.
Add a new member to the Operations workspace as an editor.
Which Zite apps are published and who owns each one?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Zite endpoint for every MCP client.
Claude, ChatGPT and Cursor reach Zite through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Zite toolbox.
Scope what Operations, Product and IT can reach in Zite, one toolbox per team.
- Operations
- Product
- Sales
- Support
ElaichiToolboxesShared connections
Share a Zite connection, never a credential.
One person connects Zite, teammates work through it without ever seeing a password or token.
- Operations
- Product
- Sales ops
- Support
ElaichiConnectionsAudit log
Every Zite change has a name on it.
See who edited which database, published which app or changed a role, and when.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 starts real Zite work.
Fetch Zite records, group them, draft a digest, approve it, post it back to Zite.
Zite digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch databases
Zite
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
Zite
Queued
Collections and dashboards
Zite health numbers without asking for them.
Four metrics, a 14 day chart and a team breakdown, refreshed on schedule, no model.
Zite health
Refreshed 4 minutes ago · every 15 minutes · from the databases collection
Databases
1,284 ↓ 12%
Apps
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Databases created
Last 14 days
By team
Share of activity
Operations 34%
Product 27%
Sales ops 21%
Support 18%
FAQ
Frequently asked questions
How do I connect Zite to Claude?
Connect Zite in Elaichi first, which opens Zite's own OAuth sign-in screen where you approve access as yourself; there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can now work with the Zite databases, apps and workspaces your account can see.
Does Zite work with ChatGPT and Cursor as well as Claude?
Yes. Once Zite 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 Zite once and every client you use picks it up.
What can an AI agent actually do with my Zite data?
An agent can look up and edit rows in your Zite databases, build and publish Zite apps, and add or change members and their roles in a workspace. Exactly what is available depends on what your Zite account has set up. Short, concrete asks such as "add a row to the leads database for Acme" work better than long paragraphs.
Does connecting Zite give the AI access to every workspace?
No. Every call into Zite runs as the person who signed in, so the agent only sees the Zite workspaces, databases and apps that person already has access to. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Zite itself allows.
Can I stop an agent from deleting or changing things in Zite?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Zite databases while blocking edits, publishing apps or changing member roles. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Zite connection when someone leaves?
Offboarding that person in Elaichi ends their access to Zite through every client at once. A Zite connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting Zite once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Zite MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Zite 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 Zite?
Yes. Both let Claude, ChatGPT or Cursor use Zite. 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 Zite call.
How is Elaichi different from Composio for Zite?
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 Zite: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Zite in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- 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.