Skip to content

Zite MCP connector

Connect Zite to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Show me every row in the customer requests database updated this week.

Working in Zite with Elaichi

  • Looked in Zite
Ask anything…
Governance / Audit log Last 24 hours
Zite Looked in Zite Emily Carter · ChatGPT · 9:41 AM Done
Zite Looked in Zite Megan Brooks · Claude · 9:38 AM Done
Zite Looked in Zite Ryan Hayes · Cursor · 9:35 AM Done

How to connect Zite to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Zite MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Zite MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Zite MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Zite MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Zite to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Zite through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Zite is logged.

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

What connecting Zite gets you

5 screens from Elaichi, each doing one job for your Zite account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask Zite a question, get a live answer.

Query Zite databases, update rows and check app status in plain language.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

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

AI apps

One Zite endpoint for every MCP client.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Zite through one governed endpoint, no SDK, no shared key.

ElaichiToolboxes
Name Source template Tools Created

Operations toolbox

Zite · internal trackers and databases

Zite starter 18 Mar 4, 2026

Product toolbox

Zite · building and publishing apps

— 9 Mar 2, 2026

Sales toolbox

Zite · lead and account databases

— 24 Feb 27, 2026

Support toolbox

Zite · request databases

Zite starter 6 Feb 19, 2026

IT toolbox

Zite · workspaces and member roles

— 31 Jan 30, 2026

HR toolbox

Zite · onboarding apps and records

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Zite toolbox.

Scope what Operations, Product and IT can reach in Zite, one toolbox per team.

ElaichiConnections
Connection Scope Status Access
ZI

Zite (Operations)

Connected by Emily Carter

Personal • Active 1 team · 6 members
ZI

Zite (Product)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
ZI

Zite (Sales ops)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
ZI

Zite (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
ZI

Zite (IT)

Connected by Ryan Hayes

Personal • Active Not shared
ZI

Zite (HR)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a Zite connection, never a credential.

One person connects Zite, teammates work through it without ever seeing a password or token.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Zite Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Zite Databases Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Zite Databases List Toolbox

Audit log

Every Zite change has a name on it.

See who edited which database, published which app or changed a role, and when.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Zite digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch databases

    Zite

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Zite

    Queued

Workflows

A schedule starts real Zite work.

Fetch Zite records, group them, draft a digest, approve it, post it back to Zite.

Zite health

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

Live

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%

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.

Why connect Zite's MCP server through Elaichi

Zite builds and runs this MCP server. Elaichi sits in front of it, so Zite's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Zite's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Zite's tools at the same Elaichi address as every other connected app. Nobody adds Zite's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Zite sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Zite's server. By default, a tool Zite does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Zite

    Zite builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Zite team.

    www.zite.com/help

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Zite, 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 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 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.

Questions, answered

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, Microsoft Copilot, 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 restricting edits, publishing apps or changing member roles. 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 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, Microsoft Copilot 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, 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 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 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