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

Source: https://elaichi.ai/connectors/zite/

## Facts

| | |
| --- | --- |
| Application | Zite |
| Category | Application Development |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Zite builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | www.zite.com/help |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Zite is connected

- 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?

## Connect Zite in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Zite.
2. Optionally set Share with, then press Connect.
3. Approve it in Zite. Zite's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Zite tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Zite MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Zite to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Zite tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Zite through Elaichi

### Keep an internal tracker current without opening it

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

### Turn a spec into a working Zite app

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

### Log a lead into the right database

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

### Find every open request for one customer

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

### Manage who is in each Zite workspace

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

### Run onboarding from a Zite app

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

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Zite connection?

Yes. One person connects Zite in Elaichi and shares the connection with a team, and nobody else ever handles a Zite credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to a Zite database or app.

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