GetGist MCP connector
The GetGist connector brings help center articles, collections, contacts, tags and events into Claude, ChatGPT and Cursor, so your team can search, update and tag GetGist records by asking, with every action logged.
-
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.
How to connect
How to connect GetGist to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect GetGist once
-
Open Connections, choose Add connection, and pick GetGist.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own GetGist app, then approve. GetGist 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.
GetGist 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.
GetGist 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.
GetGist 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 GetGist 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 GetGist through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Keep the help center current
Ask which GetGist articles mention a retired feature, then have the agent draft the corrections and update each article in its collection.
-
Marketing
Tag contacts after a campaign
After a webinar or launch, tag the GetGist contacts who showed up and untag the ones who have gone quiet, without exporting a spreadsheet.
-
Sales
Catch a contact up after a call
Tell the agent what changed on the call and it updates the GetGist contact, records the event and applies the right tag for follow-up.
-
Customer Success
Spot customers who need a nudge
Ask for GetGist contacts tagged as trial users with no recent events, then send the list to the person who owns renewals.
-
Product
Turn release notes into articles
Paste release notes and the agent creates a GetGist article in the right collection, written in the voice of your existing help center.
-
Operations
Clean up duplicate contacts and tags
Find GetGist contacts that appear twice, merge the details through an upsert, and remove tags nobody has used in months.
Try asking
- “Which GetGist articles about billing haven't been updated this year?”
- “Tag every contact who attended last week's webinar”
- “Draft a new article for the onboarding collection”
Compare
Elaichi vs Zapier MCP vs Composio for GetGist
All three can connect GetGist 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 GetGist tools | Allow or restrict single GetGist 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 GetGist 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
GetGist tools for your AI agents
59 tools are ready to call through Elaichi's MCP endpoint the moment you connect GetGist, 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 GetGist gets you
6 screens from the product, each doing one job for your GetGist account.
The agent
Ask about GetGist contacts in plain language.
Three starter prompts pull answers from live GetGist articles, contacts and tags.
- articles
- collections
- contacts
- tags
Ask Elaichi to work across your apps.
Which GetGist articles about billing haven't been updated this year?
Tag every contact who attended last week's webinar
Draft a new article for the onboarding collection
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings GetGist to every client.
Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
59 GetGist tools, ready without writing code.
Articles, collections, contacts, events and tags are covered with no custom code.
- List all GetGist articles
- Get single GetGist article by ID
- Create a GetGist article
- Update a GetGist article by ID
Toolboxes
Each team gets its own GetGist toolbox.
Support, marketing and sales each see a GetGist toolbox scoped to their work.
- Support
- Marketing
- Sales
- Customer Success
Shared connections
Teammates use GetGist without seeing a credential.
One person connects GetGist, shares it with teams, and nobody else handles a key.
- Support
- Marketing
- Sales EMEA
- Customer Success
Audit log
Every GetGist action is written down.
When, who, what happened, and which article or contact, in an append-only 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 starts real GetGist work.
New contacts are fetched, grouped, drafted into a digest, approved, then posted back to GetGist.
GetGist digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch articles
GetGist
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
GetGist
Queued
Collections and dashboards
GetGist health numbers arrive on a schedule.
Four metrics, 14 days of contacts created, and a team breakdown, computed without a model.
GetGist health
Refreshed 4 minutes ago · every 15 minutes · from the articles collection
Articles
1,284 ↓ 12%
Collections
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Articles created
Last 14 days
By team
Share of activity
Support 34%
Marketing 27%
Sales EMEA 21%
Customer Success 18%
FAQ
Frequently asked questions
How do I connect GetGist to Claude?
In Elaichi, choose GetGist and sign in; GetGist connects with an API key from your GetGist settings, and because this connector uses an OAuth application registered inside GetGist, one person brings a client ID and secret once when setting it up. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. That is the whole setup, and everyone after that first person simply signs in as themselves.
Does GetGist work with ChatGPT and Cursor as well as Claude?
Yes. Once GetGist 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 GetGist once and every client picks it up.
What can an AI agent actually do with my GetGist data?
It can search and read your GetGist help center articles and collections, create or update an article, look up a contact, add or update contacts in bulk, track an event against a contact, and tag or untag groups of contacts. Short, concrete asks work best, such as "tag everyone who attended Tuesday's webinar" rather than a long paragraph. Anything it changes shows up in GetGist right away and in the Elaichi audit log.
Does connecting GetGist give the AI access to my whole workspace?
No. The agent only sees what the person who signed in to GetGist can already see, because every call runs under that person's own GetGist access. Elaichi can narrow that further, for example read-only on articles for one team, but it can never widen what GetGist itself allows.
Can I stop an agent from deleting or changing things in GetGist?
Yes. Restrictions in Elaichi work per action, so you can block deleting GetGist articles, collections, contacts or tags while still allowing searches and updates. A restricted action is never advertised to the AI client at all, so no prompt, however it is worded, can reach it.
What happens to a GetGist connection when someone leaves?
Offboarding that person in Elaichi ends their GetGist access immediately across Claude, ChatGPT, Cursor and every other client. If they had shared a GetGist connection with a team, it keeps working for everyone else. Disconnecting GetGist once in Elaichi removes it from every client at the same time.
Does the GetGist MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. GetGist 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 GetGist?
Yes. Both let Claude, ChatGPT or Cursor use GetGist. 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 GetGist call.
How is Elaichi different from Composio for GetGist?
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 GetGist: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put GetGist 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.