Guru MCP connector
The Guru connector brings announcements, answers, team analytics and AI evaluations into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works with Guru as themselves and every call lands in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Guru announcements has the support team not read yet?
Working in Guru with Elaichi
-
List all Guru aievaluations
-
Get single Guru aievaluation by ID
-
List all Guru aievaluations exports
How to connect Guru to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Guru 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.
Guru 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.
Guru 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.
Guru 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.
Guru 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 Guru 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 Guru through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Guru is logged.
-
Support
Answer a ticket from the knowledge base
Ask for the current answer to a customer question and get it from Guru, then record a new answer when the team settles something that was missing.
-
Internal comms
Publish an announcement and chase the readers
Draft an announcement in Guru, see who has read it and who has not, and send a reminder to the people who still need to.
-
Enablement
See which teams actually use Guru
Pull team analytics and user stats to find the teams that read what you publish and the ones that quietly stopped.
-
People
Keep policy updates acknowledged
Push a policy change out as a Guru announcement, track reads across the company, and export the list when HR needs proof.
-
Operations
Check the quality of AI answers
Run an AI evaluation in Guru, review the results, and export them so the team can decide what content needs fixing.
-
Sales
Route open questions to the right expert
Assign unanswered Guru questions to the person who knows, restore an answer that was removed by mistake, and keep the sales floor from guessing.
Try asking
- “Which Guru announcements has the support team not read yet?”
- “Summarize this week's Guru team analytics for sales enablement.”
- “Draft a Guru announcement about the new refund policy and send reminders.”
What connecting Guru gets you
6 screens from Elaichi, each doing one job for your Guru account.
Ask Elaichi to work across your apps.
Which Guru announcements has the support team not read yet?
Summarize this week's Guru team analytics for sales enablement.
Draft a Guru announcement about the new refund policy and send reminders.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Guru questions in plain words.
Three starter prompts read live announcements, answers and team analytics straight from Guru.
Copy the endpoint
AI apps
One endpoint brings Guru to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot sign in over OAuth, no SDK and no shared API key.
Tool catalog
253 Guru tools, no custom code.
Announcements, answers, analytics and AI evaluations are covered the day Guru is connected.
Toolboxes
Every team gets its own Guru toolbox.
Support, sales and people teams each see only the Guru tools their work needs.
Shared connections
Share a Guru connection, never a credential.
One person connects Guru, teammates work through it without ever seeing the API key.
Audit log
Every Guru call is written down.
When, who, what happened and which announcement or answer, 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.
Guru digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch announcements
Guru
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
Guru
Queued
Workflows
A schedule drafts the Guru digest itself.
New Guru announcements are fetched, grouped, drafted, approved by a person, then posted back.
Guru health
Refreshed 4 minutes ago · every 15 minutes · from the announcements collection
Announcements
1,284 ↓ 12%
Answers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Announcements created
Last 14 days
By team
Share of activity
Support 34%
Sales enablement 27%
People ops 21%
Product 18%
Collections and dashboards
Guru health numbers, computed without a model.
Four metrics, 14 days of announcements created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Guru
All three can connect Guru 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 Guru tools | Allow or restrict single Guru 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 Guru 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.
Guru tools for your AI agents
253 tools are ready to call through Elaichi's MCP endpoint the moment you connect Guru, 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 Guru to Claude?
Connect Guru in Elaichi first by pasting a Guru API key, which is the only sign-in step Guru needs. There is no OAuth app to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs in to Elaichi and Guru is ready to use.
Does Guru work with ChatGPT and Cursor as well as Claude?
Yes. Guru is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses the same Guru connection without any extra setup.
What can an AI agent actually do with my Guru data?
With Guru connected, an agent can read and create announcements, send read reminders, see who has read what, record or assign answers, pull team analytics and user stats, and run or review AI evaluations. Short, concrete asks work best, such as who has not read this week's Guru announcement, rather than a long paragraph of instructions.
Does connecting Guru give the AI everything in my Guru workspace?
No. Every call to Guru runs inside the access of the person who signed in, so an agent sees only the Guru announcements, answers and analytics that person can already see. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Guru itself allows.
Can I stop an agent from deleting or changing things in Guru?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Guru announcements and answers while restricting deletion or edits. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Guru connection when someone leaves?
Offboarding a person in Elaichi ends their access to Guru through every client at once. A Guru connection shared with a team keeps working for everyone else. Disconnecting Guru once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.
Does the Guru MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Guru 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 Guru?
Yes. Both let Claude, ChatGPT or Cursor use Guru. 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 Guru call.
How is Elaichi different from Composio for Guru?
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 Guru: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Guru 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