Quip MCP connector
The Quip connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent search, read, create, and edit Quip documents and chat threads as the signed-in person, with every action recorded in an audit log.
-
How it connects. OAuth or 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.
How to connect
How to connect Quip to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Quip once
-
Open Connections, choose Add connection, and pick Quip.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Quip app, then approve. Quip needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
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.
Quip 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.
Quip 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.
Quip 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 Quip 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 Quip through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch the account plan up after a call
Find the account plan in Quip, add the notes from this afternoon's call, and drop the new next steps into the document without opening a browser tab.
-
Operations
Start the weekly review from a template
Copy last week's operations review document, rename it for this week, and add the people who need to fill in their sections.
-
People
Build a new hire's reading list
Search Quip for the onboarding guides a new teammate needs and add them as a member on each thread in one pass.
-
Product
Lock a spec once it is signed off
When a product spec is approved, lock edits on the whole document or just the decision section so nobody quietly rewrites it later.
-
Support
Find the runbook without asking around
Search recent Quip threads for the escalation runbook, pull out the relevant steps, and paste the answer into the ticket you are working.
-
IT
Tidy up threads that moved elsewhere
Mark documents that now live in another system as moved, remove members who left the project, and tighten share link settings across a batch of threads.
Try asking
- “Summarize this week's updates across our Quip threads.”
- “Find the latest draft document shared with the design team.”
- “List Quip threads created by the support team this month.”
Compare
Elaichi vs Zapier MCP vs Composio for Quip
All three can connect Quip 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 Quip tools | Allow or restrict single Quip 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 Quip 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
Quip tools for your AI agents
107 tools are ready to call through Elaichi's MCP endpoint the moment you connect Quip, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Quip gets you
6 screens from the product, each doing one job for your Quip account.
The agent
Ask Quip and get real answers back.
Type a plain question and pull answers straight from live Quip threads and documents.
- threads
- documents
- users
- chats
Ask Elaichi to work across your apps.
Summarize this week's updates across our Quip threads.
Find the latest draft document shared with the design team.
List Quip threads created by the support team this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Quip endpoint, every client connects.
Claude, ChatGPT and Cursor reach Quip through one governed org endpoint, no sdk needed.
Copy the endpoint
Tool catalog
107 Quip tools, ready with no code.
Every Quip user, thread and document action is cataloged and ready to call.
- List all Quip users
- Quip users get current
- Get single Quip user by ID
- Quip users list contacts
Toolboxes
Every team gets its own Quip toolbox.
Docs, support and engineering each work from a toolbox scoped to their own Quip needs.
- Docs
- Support
- Engineering
- Sales
Shared connections
Share Quip access without sharing credentials.
See who connected each Quip account and how many teams and members use it.
- Docs Team
- Support
- Engineering
- Sales
Audit log
Every Quip action, logged and attributable.
See when, who and what happened across every Quip call in one audit log.
- When
- Who
- What happened
- Type
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 triggers real Quip work.
A trigger fetches Quip threads, groups them, drafts a digest, waits for approval, then posts back.
Quip digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch threads
Quip
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
Quip
Queued
Collections and dashboards
Quip metrics that refresh on their own.
A 14 day chart of records created and a team breakdown, computed with no model involved.
Quip health
Refreshed 4 minutes ago · every 15 minutes · from the threads collection
Threads
1,284 ↓ 12%
Documents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Threads created
Last 14 days
By team
Share of activity
Docs Team 34%
Support 27%
Engineering 21%
Sales 18%
FAQ
Frequently asked questions
How do I connect Quip to Claude?
Connect Quip in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Quip asks you to register an OAuth application inside Quip and bring its client ID and secret to Elaichi once, or you can use a Quip API key instead. After that, each person signs in to Quip with their own account and nobody else on the team handles a credential.
Does Quip work with ChatGPT and Cursor as well as Claude?
Yes. Once Quip 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 Quip once and every client sees it.
What can an AI agent actually do with my Quip data?
An agent connected to Quip can search your documents and chat threads, read a document and answer questions about it, create a new document or chat, edit an existing one, copy a document to reuse it, add or remove members, lock edits, and change share link settings. Because Quip exposes many actions, the agent looks them up as it goes, so short concrete asks like "add Priya to the Q3 plan" work better than long paragraphs.
Does connecting Quip give the AI access to every document in our workspace?
No. Access to Quip follows the person who signed in, so the agent can only see the documents and threads that person can already open in Quip. Elaichi can narrow that further with restrictions, but it can never give an agent more of Quip than the signed-in person has.
Can I stop an agent from deleting or changing things in Quip?
Yes. Restrictions in Elaichi work per action, so you can allow searching and reading Quip documents while blocking edits, deletion, or member changes. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt can reach it.
What happens to a Quip connection when someone leaves?
Offboarding that person in Elaichi ends their Quip access through every AI client at once. If they had shared a Quip connection with the team, it keeps working for everyone else. Disconnecting Quip once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.
Does the Quip MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Quip 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 Quip?
Yes. Both let Claude, ChatGPT or Cursor use Quip. 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 Quip call.
How is Elaichi different from Composio for Quip?
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 Quip: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Quip 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.