Grain MCP connector
The Grain connector brings your recorded meetings, transcripts, AI notes and action items into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can search, summarize and clip calls inside their own Grain access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize action items from this week's customer calls.
Working in Grain with Elaichi
-
Looked in Grain
How to connect Grain to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Grain 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.
Grain 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.
Grain 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.
Grain 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.
Grain 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 Grain 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 Grain through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Grain is logged.
-
Sales
Catch up on a deal before the next call
Ask for the AI notes and open action items from the last three Grain calls with an account, then walk in knowing what was promised and by whom.
-
Customer Success
Pull every commitment from a renewal conversation
List the action items across a quarter of Grain meetings with one customer and check which ones are still outstanding before the renewal review.
-
Support
Find the moment a customer described the bug
Search Grain transcripts for the error a customer mentioned, read the exact wording, and clip that passage to attach to the ticket.
-
Product
Gather feature requests from the week's calls
Search Grain meetings for mentions of a feature, tag the ones that matter, and collect the clips into a playlist the product team can watch.
-
Marketing
Turn customer calls into a highlight reel
Find Grain meetings where customers describe results in their own words, create clips, and add them to a playlist for the case study team.
-
Enablement
Build a coaching playlist from real calls
Pick strong objection handling moments from Grain transcripts, clip them, and manage a playlist that new reps watch in their first week.
Try asking
- “Summarize action items from this week's customer calls.”
- “Find meetings where pricing came up and clip those moments.”
- “Add yesterday's demo recordings to the onboarding playlist.”
What connecting Grain gets you
5 screens from Elaichi, each doing one job for your Grain account.
Ask Elaichi to work across your apps.
Summarize action items from this week's customer calls.
Find meetings where pricing came up and clip those moments.
Add yesterday's demo recordings to the onboarding playlist.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any recorded call in plain language.
Search Grain meetings, read transcripts and AI notes, and pull action items by asking.
Copy the endpoint
AI apps
Grain works in every MCP client you use.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Grain through one governed endpoint, no SDK, no shared API key.
Toolboxes
Each team gets its own Grain toolbox.
Give Sales, Support and Product their own Grain toolboxes, each scoped to one team.
Shared connections
Share one Grain connection, keep the credential private.
Teammates work through a shared Grain account and never see a password or token.
Audit log
Every Grain action is logged, with a name.
When, who, what happened and which meeting or clip, 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.
Grain digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch meetings
Grain
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
Grain
Queued
Workflows
A schedule turns Grain calls into a digest.
New Grain meetings are fetched, grouped, drafted into a digest, approved, then posted back.
Grain health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
Meetings
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Meetings created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales Americas 27%
Customer Success 21%
Support 18%
Collections and dashboards
Grain meeting health, computed, not asked for.
Four metrics, 14 days of meetings recorded and a team breakdown, refreshed on schedule, no model.
Why connect Grain's MCP server through Elaichi
Grain builds and runs this MCP server. Elaichi sits in front of it, so Grain'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 Grain's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Grain's tools at the same Elaichi address as every other connected app. Nobody adds Grain'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 Grain 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 Grain's server. By default, a tool Grain 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 Grain
Grain builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Grain team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Grain
All three can connect Grain 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 Grain tools | Allow or restrict single Grain 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 Grain 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 Grain to Claude?
Connect Grain in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Grain connects over OAuth, so you sign in to your own Grain account in a browser window and approve the connection. There is no OAuth application to register and no client ID or secret to generate.
Does Grain work with ChatGPT and Cursor as well as Claude?
Yes. Once Grain is connected in Elaichi, the same endpoint works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Grain once and every client picks it up.
What can an AI agent actually do with my Grain data?
An agent can search your Grain meetings, read transcripts and AI notes, and list the action items that came out of a call. It can also create clips, tag meetings and manage playlists on your behalf. Short concrete asks such as "action items from Tuesday's onboarding call" work better than long sentences.
Does connecting Grain give the AI access to every recording in the workspace?
No. Every call runs inside the Grain access of the person who signed in, so the agent sees only the meetings, transcripts and clips that person can already open in Grain. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Grain?
Yes. Restrictions in Elaichi work per action, so you can allow reading Grain transcripts and notes while restricting tagging, clipping or playlist changes. 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 Grain connection when someone leaves?
Offboarding that person in Elaichi ends their access to Grain through every client at once. A Grain connection they shared keeps working for everyone else on the team. Disconnecting Grain once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Grain MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Grain 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 Grain?
Yes. Both let Claude, ChatGPT or Cursor use Grain. 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 Grain call.
How is Elaichi different from Composio for Grain?
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 Grain: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Grain 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