Cursor MCP connector
Connect Cursor to Elaichi and Claude, ChatGPT, Microsoft Copilot or any MCP client can answer questions about Cursor users, daily usage, team spend, audit logs and analytics, inside each person's own access, with every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Who on the team used Cursor every day this week?
Working in Cursor with Elaichi
-
List all Cursor users
-
List all Cursor audit logs
-
List all Cursor daily usage data
How to connect Cursor to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Cursor 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.
Cursor 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.
Cursor 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.
Cursor 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.
Cursor 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 Cursor 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 Cursor through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Cursor is logged.
-
Engineering
See who is actually using Cursor
Ask which engineers are active every day, who sits at the top of the leaderboard, and whose agent edits and tab completions have gone quiet since the last sprint.
-
Finance
Reconcile Cursor spend before the invoice lands
Pull team spend and plan assignments for the month, compare them with daily usage, and spot seats that cost money without producing a single edit.
-
IT
Check Cursor client versions across the company
List every user and the client version they are running, then find the people still on an old build before rolling out a required update.
-
Security
Answer an audit question in minutes
Filter Cursor audit logs by person, date or event type when someone asks who changed a setting or which accounts were added last week.
-
Developer experience
Learn how the team really uses Cursor
Review which models, commands, skills, MCP servers and file extensions get the most use, then shape onboarding and guidance around what engineers actually do.
-
Operations
Build the weekly Cursor adoption update
Gather daily active users, ask mode usage, Bugbot activity and conversation insights into one summary for leadership without exporting a spreadsheet.
Try asking
- “Who on the team used Cursor every day this week?”
- “Summarize our Cursor team spend by plan for this month.”
- “Which models did the platform team use most in Cursor last week?”
What connecting Cursor gets you
6 screens from Elaichi, each doing one job for your Cursor account.
Ask Elaichi to work across your apps.
Who on the team used Cursor every day this week?
Summarize our Cursor team spend by plan for this month.
Which models did the platform team use most in Cursor last week?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Cursor usage questions in plain language.
Get answers from live Cursor users, spend and analytics without opening a dashboard.
Copy the endpoint
AI apps
Cursor data in every client, one endpoint.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
All 288 Cursor tools, no custom code.
Users, audit logs, usage events, spend and team analytics, ready to search and run.
Toolboxes
Each team gets its own Cursor toolbox.
Finance sees spend, Security sees audit logs, Engineering sees adoption, each in a scoped toolbox.
Shared connections
Teammates use Cursor without touching the API key.
One person connects Cursor, shares it, and the credential never reaches anyone else.
Audit log
Every Cursor call is recorded, with a name.
When, who, what happened and which record, 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.
Cursor digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Cursor
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
Cursor
Queued
Workflows
A schedule starts the Cursor digest, you approve.
Usage events are fetched, grouped, drafted into a digest, approved, then posted back to Cursor.
Cursor health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Audit logs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Engineering 34%
Finance 27%
IT 21%
Security 18%
Collections and dashboards
Cursor health numbers, computed, never asked for.
Four metrics, 14 days of usage events, and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Cursor
All three can connect Cursor 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 Cursor tools | Allow or restrict single Cursor 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 Cursor 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.
Cursor tools for your AI agents
288 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cursor, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 235 of 288 Cursor tools here. Connect Cursor and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Cursor to Claude?
First connect Cursor in Elaichi, which asks for a Cursor admin API key that you create in Cursor's dashboard and paste in. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in as yourself and Claude can start answering questions about Cursor users, usage and spend.
Does Cursor work with ChatGPT and Cursor itself as well as Claude?
Yes. Once Cursor is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. You connect Cursor once, and every client your team uses picks it up.
What can an AI agent actually do with my Cursor data?
An agent can read what a Cursor admin can see in the dashboard: the list of users, audit logs, daily usage, team spend, usage events and the analytics on agent edits, tabs, models, commands, skills, client versions, Bugbot and the leaderboard, for the whole team or one person. In practice that means asking who used Cursor this week, what the platform team spent, or which models engineers prefer, and getting an answer from live Cursor records. Short, concrete asks work better than long sentences.
Does connecting Cursor give the AI everything in my Cursor team?
No. Every call to Cursor runs under the person who signed in to Elaichi, so an agent sees only what that person is allowed to see. Elaichi can then narrow that further with roles and restrictions, so Finance might get spend and plans while Security gets audit logs, and it never widens access beyond what Cursor itself grants.
Can I stop an agent from changing or exposing things in Cursor?
The Cursor connector reads records such as users, usage, spend and audit logs; it does not change them. You can still restrict any individual action in Elaichi on a role or on one person, for example keeping team spend or per-user analytics away from everyone outside Finance. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Cursor connection when someone leaves?
Offboarding a person in Elaichi ends their access to Cursor through every client at once. A Cursor connection shared with the team keeps working for everyone else, because it is not tied to the leaver's sign-in. If you want Cursor gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Cursor MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Cursor 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 Cursor?
Yes. Both let Claude, ChatGPT or Cursor use Cursor. 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 Cursor call.
How is Elaichi different from Composio for Cursor?
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 Cursor: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Cursor 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