GetGist MCP connector
The GetGist connector brings help center articles, collections, contacts, tags and events into Claude, ChatGPT, Cursor and Microsoft Copilot, so your team can search, update and tag GetGist records by asking, with every action logged.
- OAuth or API key
- Free 14-day trial
- No credit card
Which GetGist articles about billing haven't been updated this year?
Working in GetGist with Elaichi
-
List all GetGist articles
-
Get single GetGist article by ID
-
GetGist articles search
How to connect GetGist to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
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. 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.
GetGist MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 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.
What teams do with GetGist through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in GetGist is logged.
-
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”
What connecting GetGist gets you
6 screens from Elaichi, each doing one job for your GetGist account.
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, Cursor or Microsoft Copilot
The agent
Ask about GetGist contacts in plain language.
Three starter prompts pull answers from live GetGist articles, contacts and tags.
Copy the endpoint
AI apps
One endpoint brings GetGist to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot share one governed endpoint, no SDK and no shared API key.
Tool catalog
59 GetGist tools, ready without writing code.
Articles, collections, contacts, events and tags are covered with no custom code.
Toolboxes
Each team gets its own GetGist toolbox.
Support, marketing and sales each see a GetGist toolbox scoped to their work.
Shared connections
Teammates use GetGist without seeing a credential.
One person connects GetGist, shares it with teams, and nobody else handles a key.
Audit log
Every GetGist action is written down.
When, who, what happened, and which article or contact, in an append-only log.
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.
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 Jake Morgan
Approve Deny -
Post the digest
GetGist
Queued
Workflows
A schedule starts real GetGist work.
New contacts are fetched, grouped, drafted into a digest, approved, then posted back to GetGist.
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%
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.
For IT and engineering
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 | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 role, 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 restrict deleting GetGist articles, collections, contacts or tags while still allowing searches and updates. 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 GetGist connection when someone leaves?
Offboarding that person in Elaichi ends their GetGist access immediately across Claude, ChatGPT, Cursor, Microsoft Copilot 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, 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 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 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