# 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.

Source: https://elaichi.ai/connectors/cursor/

## Facts

| | |
| --- | --- |
| Application | Cursor |
| Category | Application Development |
| AI tools | 288 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Cursor is connected

- 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?

## Connect Cursor in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Cursor.
2. Optionally set Share with, then press Connect.
3. Paste a Cursor API key. One person generates a token in Cursor and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Cursor tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Cursor MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Cursor MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Cursor tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Cursor through Elaichi

### See who is actually using Cursor

Engineering. 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.

### Reconcile Cursor spend before the invoice lands

Finance. 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.

### Check Cursor client versions across the company

IT. 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.

### Answer an audit question in minutes

Security. Filter Cursor audit logs by person, date or event type when someone asks who changed a setting or which accounts were added last week.

### Learn how the team really uses Cursor

Developer experience. Review which models, commands, skills, MCP servers and file extensions get the most use, then shape onboarding and guidance around what engineers actually do.

### Build the weekly Cursor adoption update

Operations. Gather daily active users, ask mode usage, Bugbot activity and conversation insights into one summary for leadership without exporting a spreadsheet.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Cursor connection?

Yes. One admin connects Cursor with the API key, shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Cursor question, not a shared account.

### 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.

## All 288 Cursor tools

Every tool below is callable through https://api.elaichi.ai/mcp once Cursor is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Cursor users** (List). List all members of your Cursor team with their details. Returns: id, email, name, role, isRemoved.
- **List all Cursor audit logs** (List). List Cursor team audit log events with filtering by time range, event type, or users. Returns oldest-first events including event_id, timestamp, user_email, event_type, application_type, and event_data. Optional: startTime, endTime, eventTypes, search, users. Date range cannot exceed 30 days; up to 500 events per page.
- **List all Cursor daily usage data** (List). List Cursor daily usage metrics per team member for a date range. Returns: userId, day, date, isActive, email, totalLinesAdded, totalLinesDeleted, acceptedLinesAdded, acceptedLinesDeleted, mostUsedModel, and 16 more. Required: startDate, endDate (epoch ms). Date range max 30 days; data aggregated hourly; paginated responses cover all team members.
- **List all Cursor team spend** (List). List per-member spend for the current Cursor billing cycle. Returns each member's userId, name, email, role, spendCents, overallSpendCents, fastPremiumRequests, and spending-limit fields. Supports searchTerm filtering and sorting by amount, date, or user.
- **List all Cursor filtered usage events** (List). List Cursor team usage events filtered by date range, user, service account, cloud agent run, automation, or hosting type. Returns per event: timestamp, userEmail, model, kind, requestsCosts, tokenUsage, chargedCents, and cursorTokenFee. Data is aggregated hourly — poll at most once per hour.
- **List all Cursor analytics team agent edits** (List). List Cursor team analytics for agent edits — AI-suggested edits accepted by the team — over a date range. Returns: id, attributes.
- **List all Cursor analytics team tabs** (List). List team-level tab autocomplete usage analytics for Cursor over an optional date range, optionally filtered by users. Returns tab usage records with metric-specific fields.
- **List all Cursor analytics team dau** (List). List daily active users for the team from the Cursor Analytics API, including the per-surface breakdown. Returns: cli_dau, cloud_agent_dau, bugbot_dau. Supports optional startDate, endDate, and users filters.
- **List all Cursor analytics team client versions** (List). List the distribution of Cursor client versions used across the team over a given date range. Returns: clientVersion.
- **List all Cursor analytics team models** (List). List model usage metrics for your Cursor team over a date range. Returns per-model usage records with an id and attributes holding the usage aggregates. Optional: startDate, endDate, users.
- **List all Cursor analytics team top file extensions** (List). List Cursor's team-wide top 5 file extensions per day, ranked by AI suggestion volume, aggregated across the team. Returns the record under its id plus the daily aggregation payload in data; defaults to the last 7 days of activity.
- **List all Cursor analytics team mcp** (List). List MCP tool adoption metrics for a Cursor team, grouped by tool_name and mcp_server_name. Returns: tool_name, mcp_server_name, start_date, end_date. Optional filters: start_date, end_date, users.
- **List all Cursor analytics team commands** (List). List command adoption analytics for a Cursor team, aggregated by command name. Returns: id, attributes.
- **List all Cursor analytics team plans** (List). List plan mode adoption analytics for your Cursor team, broken down by model, over the requested date range. Returns the plan mode adoption dataset with metric-specific fields.
- **List all Cursor analytics team skills** (List). List Cursor team skill-adoption analytics, aggregated by skill name over an optional date range. Returns: id, attributes. Optional: startDate, endDate, users; the range defaults to the last 7 days.
- **List all Cursor analytics team ask mode** (List). List Cursor Analytics team ask mode adoption metrics grouped by model. Returns a collection of per-model ask mode adoption records; the upstream docs do not enumerate the individual record fields.
- **List all Cursor analytics team conversation insights** (List). Get aggregated conversation insights for a Cursor team over a date range, optionally filtered by user. Returns breakdowns by intents, complexity, categories, guidanceLevels, and workTypes — each present when requested. Required: include. Pass include as a comma-separated string or repeated query parameters.
- **List all Cursor analytics team leaderboard** (List). List the team's Cursor AI-usage leaderboard, ranking members by combined Tab and Agent usage over a date range. Returns: id, attributes. Max 500 per page.
- **List all Cursor analytics team bugbot** (List). List per-PR Bugbot analytics for the team in Cursor, optionally filtered by date range, repository, and pull request state. Returns per-PR Bugbot analytics records with metric-specific fields. Optional: startDate, endDate, prState, repo.
- **List all Cursor analytics by user agent edits** (List). List accepted Agent (Composer) edits per user from the Cursor Analytics API. Returns: userId, composerLinesAdded, composerLinesDeleted.
- **List all Cursor analytics by user tabs** (List). List Tab usage metrics by user in Cursor's Analytics API. Returns per-user Tab usage records with an id and content-specific usage attributes; the remaining record fields are specific to Cursor's Analytics API. Enterprise teams only.
- **List all Cursor analytics by user models** (List). List Cursor Analytics model usage per user. Returns the data payload of per-user records, each keyed by an id with model-usage-specific attributes. Optional filters: startDate, endDate, users.
- **List all Cursor analytics by user top file extensions** (List). List the top file extensions by user from the Cursor Analytics API. Returns per-user rows including id and content-specific analytics fields (attributes).
- **List all Cursor analytics by user client versions** (List). List Cursor client versions by user from the Analytics API. Returns per-user client-version records: id, attributes (fields defined upstream). Optional: startDate, endDate, users.
- **List all Cursor analytics by user mcp** (List). List per-user MCP adoption analytics for your Cursor team over a reporting window. Returns per-user records with id and adoption details in attributes (tracked per MCP tool and MCP server). Optional filters: startDate, endDate, users.
- **List all Cursor analytics by user commands** (List). List per-user commands adoption metrics from Cursor's Analytics API, with one record per user covering their Cursor command usage over the requested date range. Returns metric-specific fields that vary per report — each record includes an id and its adoption attributes.
- **List all Cursor analytics by user plans** (List). List per-user plans adoption analytics from Cursor's Analytics API. Returns aggregated plan-adoption records, one per user, from the response's data collection; Cursor's documentation does not enumerate the record's fields.
- **List all Cursor analytics by user skills** (List). List Cursor skills-adoption analytics aggregated by user over a date range. Returns per-user records with an id and metric-specific attributes.
- **List all Cursor analytics by user ask mode** (List). List ask-mode adoption analytics per Cursor user. Returns one record per user with id and content-type-specific usage attributes (the upstream docs do not enumerate the per-user ask-mode fields).
- **Delete a Cursor app installation by ID** (Delete). Delete an app installation that belongs to the authenticated Cursor app, identified by id. Returns an empty 204 response on success. A 404 does not distinguish a missing installation from one the app cannot access. Required: id.
- **Get single Cursor app installation by ID** (Get). Get a single Cursor app installation by id. Returns: id, appId, target, createdAt, updatedAt, repoSelectionMode, scopes, installedBy, suspendedAt, deletedAt. Required: id.
- **List all Cursor app installations** (List). List Cursor app installations for the authenticated app. Returns: id, appId, target, createdAt, updatedAt, repoSelectionMode, scopes, installedBy, suspendedAt, deletedAt. Max 100 per page.
- **Cursor app signing keys bulk delete** (Delete). Revoke a Cursor Origin app signing key by its key ID. JWTs signed with a revoked key stop authenticating; the last active signing key cannot be revoked. Returns an empty 204 response on success. Required: app_id, kid.
- **Create a Cursor app signing key** (Create). Add a signing key to a Cursor app. Returns: kid, createdAt. Adding a key beyond the app's active signing key limit is rejected until another key is revoked; registering an already-registered key is also rejected. Required: app_id, app_id, publicKey.
- **List all Cursor branches** (List). List the branches of a Cursor repository together with each branch's tip commit, sorted in ascending name order. Returns: name, commit. Max 100 per page. Required: owner_slug, repo_name.
- **Create a Cursor check run annotation** (Create). Atomically append 1–25 annotations to a Cursor check run; the run stores at most 100 annotations and the operation is not idempotent, so retries may append duplicates. Returns the annotations array with id, check_run_id, annotationLevel, message, title, and location. Required: owner_slug, repo_name, check_run_id, annotations.
- **List all Cursor check run annotations** (List). List a Cursor check run's annotations in ascending id order. Returns: id, annotationLevel, message, title, rawDetails, createdAt, updatedAt, location. Default 30, max 100 per page. Required: owner_slug, repo_name, check_run_id.
- **Create a Cursor check run rerequest** (Create). Re-request a check run in Cursor: asks the app that reported the run to run it again and notifies it via the repository.check_run.rerequested webhook. Returns the updated check run — id, status (`rerequested`), rerequestedAt, rerequestedBy, conclusion, output. The run must be completed, declared…. Required: owner_slug, repo_name, check_run_id,…
- **Cursor check runs batch upsert** (Upsert). Atomically upsert up to 10 check runs for one check suite in Cursor. Returns: checkSuite, checkRuns, results. Every run commits or the whole request rolls back, and run identities must be unique by (external_id, key). Required: owner_slug, repo_name, headSha, checkSuite, checkRuns.
- **Create a Cursor check run** (Create). Upsert a check suite plus a check run in Cursor for a repository commit. Repeating the same suite and run keys updates in place instead of creating a duplicate. Returns: checkSuite, checkRun, outcome. Requires: owner_slug, repo_name, headSha, checkSuite, checkRun. Required: owner_slug, repo_name, headSha, checkSuite, checkRun.
- **Get single Cursor check run by ID** (Get). Get a single Cursor check run by its server-assigned id (cr_…). Returns: id, repository, checkSuite, sha, baseSha, key, name, status, conclusion, detailsUrl, externalUpdatedAt, startedAt, completedAt, createdAt, updatedAt, and 7 more fields. Required: id, owner_slug, repo_name.
- **Get single Cursor check suite by ID** (Get). Get a Cursor check suite by its server-assigned id. Returns: id, repository, sha, baseSha, key, name, detailsUrl, createdAt, updatedAt, externalId, actor. Does not embed check runs; fetch them separately. Required: id, owner_slug, repo_name.
- **Create a Cursor inbound IP allowlist entry** (Create). Add an entry to a Cursor namespace's inbound IP allowlist. Returns: id, cidr, description, enabled, createdAt. A /0 range or a list already holding 1000 entries is rejected; enabled defaults to true. Required: namespace_slug, cidr.
- **Delete a Cursor inbound IP allowlist entry by ID** (Delete). Delete an inbound IP allowlist entry from a Cursor namespace by id. Returns an empty 204 response on success. Removing the entry that admits the caller's own address from an enforced list is rejected. Required: id, namespace_slug.
- **Get single Cursor inbound IP allowlist entry by ID** (Get). Get a single inbound IP allowlist entry by id in a Cursor namespace. Returns: id, cidr, description, enabled, createdAt. Required: id, namespace_slug.
- **Cursor inbound IP allowlist entries replace** (Action). Atomically replace every entry on a Cursor namespace's inbound IP allowlist. Returns: allowlist, addedCount, updatedCount, removedCount, unchangedCount. Max 1000 entries; an empty entries requires allowEmpty. Required: namespace_slug.
- **Update a Cursor inbound IP allowlist entry by ID** (Update). Update an inbound IP allowlist entry by id in a Cursor namespace; omitted fields keep their stored values and a new cidr keeps the entry's id. Returns: id, cidr, description, enabled, createdAt. Required: id, namespace_slug.
- **Create a Cursor installation access token** (Create). Create a short-lived installation access token for the authenticated Cursor app, scoped to a single installation. Returns: token, expiresAt. The token expires within 15 minutes — mint a new one rather than caching. Required: installation_id, installation_id.
- **Create a Cursor installation repo** (Create). Add repositories to a Cursor app installation's repository selection. Returns the updated installation: id, appId, target, createdAt, repoSelectionMode, scopes. Additive only — listed repos are unioned with the current selection and must all belong to the namespace. Required: namespace_slug, installation_id, repoIds.
- **List all Cursor installation repos** (List). List repositories accessible to the authenticated Cursor app installation. Returns: id, name, fullName, owner, defaultBranch, createdAt, updatedAt, pushedAt, cloneUrl, mirror, visibility, allowMergeCommit, allowSquashMerge, deleteBranchOnMerge, webUrl. Max 100 per page.
- ...and 238 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
