cursor-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cursor-mcp check my spend summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cursor-mcp
FastMCP 3.2 server for Cursor platform APIs — spend guardrails, cloud agent monitoring, and inter-agent inbox.
Complements cursor-app-control (IDE/Glass). Does not replace it.
Port | Role |
11000 | HTTP |
stdio | Cursor |
MCD: CHANGELOG_DIGEST_JUN_2026.md · CURSOR_MCP_PROPOSAL.md
Quick start
cd D:\Dev\repos\cursor-mcp
Copy-Item .env.example .env
# Edit .env — set CURSOR_API_KEY (and CURSOR_ADMIN_API_KEY for full spend API)
uv sync
.\start.ps1 -ServeCursor mcp.json
{
"mcpServers": {
"cursor-mcp": {
"command": "D:\\Dev\\repos\\cursor-mcp\\.venv\\Scripts\\python.exe",
"args": ["-m", "cursor_mcp", "--stdio"],
"env": {
"CURSOR_API_KEY": "cursor_...",
"CURSOR_ADMIN_API_KEY": "crsr_..."
}
}
}
}Related MCP server: cursor-usage
Tools
cursor_usage
Operation | Purpose |
| Main guardrail — hourly spend, on-demand, running cloud agents, cache delta |
| One-shot dashboard replacement |
| Admin API |
| Last N hours usage events (sum |
| Show configured thresholds |
| API key identity |
cursor_cloud
Operation | Purpose |
| All cloud agents — spot runaway parallelism |
| Single agent |
| Runs for agent |
| Cancel a run (use sparingly) |
cursor_inbox
Structured message drop for Cursor agents. Any process posts; agent polls at task start.
Operation | Purpose |
| Drop a message (subject, body, priority, tags, optional payload dict) |
| Poll unread — call at agent task start |
| Full message by id |
| Acknowledge (moves to |
| Acknowledge all unread |
| Delete acked messages older than N days |
Drop dir: CURSOR_INBOX_DIR env (default ~/.cursor-mcp/inbox/). No daemon, no network — pure JSON files.
Who can write:
Claude Desktop:
cursor_inbox post(add cursor-mcp to Claude Desktop MCP config)meta_mcp / any fleet server: direct JSON file drop to
CURSOR_INBOX_DIRPowerShell / Python scripts: same
Sandra:
cursor_inbox postfrom any MCP client
Cursor agent convention: add cursor_inbox list to AGENTS.md or Cursor rules so agents check for messages at the start of every session.
cursor_docs
Fleet snippets. Topics: cloud-agents, profiles, mcp-config, spend-guardrails, cursor-mcp, cursor-inbox, sdk-jun-2026, design-mode, auto-review, context-canvas, changelog-jun-2026.
cursor_sdk
Read-only SDK guidance (no agent spawn): capabilities, upgrade_notes, autoreview_template, custom_tools_guide, store_options.
Starter permissions: docs/permissions.fleet.example.json
cursor_help
Tool index and setup. Always current.
Auth notes
Key | Endpoints |
|
|
|
|
Individual Pro without Admin API: alert_check still works via cloud agent count + cache; spend/events show partial_errors until you add a team admin key.
Poll at most every 1–2 hours — Admin API aggregates hourly.
Env
Variable | Default | Purpose |
| — | User key, required |
| — | Team admin key, optional |
|
| HTTP bind |
|
| HTTP port |
|
| Message drop dir |
|
| ~$3/h warn |
|
| ~$20 on-demand warn |
|
| Parallel agents warn |
| — | Filter spend by email |
Copy .env.example. Never commit real keys.
Fritz task
Scheduled coworker_cursor_spend_watch — every 2 hours, emails on warn or critical.
See docs/FRITZ_INTEGRATION.md.
MCPB (Claude Desktop)
uv sync
just mcpb-pack
# → dist/cursor-mcp-v0.2.0.mcpb — drag into Claude Desktop ExtensionsRequires uv on PATH. Set CURSOR_API_KEY / CURSOR_ADMIN_API_KEY in the extension env.
Changelog
See CHANGELOG.md. Current: v0.2.0 (2026-06-07) — cursor_inbox + MCPB packaging.
Available Tools
6 toolscursor_cloudA
List and inspect Cursor cloud agents (read-first; cancel is gated).
Runaway spend often correlates with many parallel cloud agents — list often.
Inputs: operation (required), agent_id, run_id, limit. Returns: object
cursor_docsB
Return fleet-curated Cursor documentation snippets.
Inputs: topic (required). Returns: object
cursor_helpA
List cursor-mcp tools and setup.
Inputs: no named parameters. Returns: object
cursor_inboxA
Inter-agent message drop for Cursor agents.
Any process writes a message to the shared inbox dir (CURSOR_INBOX_DIR). The Cursor agent calls cursor_inbox to poll, read, and acknowledge.
Typical flow:
Claude Desktop / meta_mcp / a script calls 'post' to leave a heads-up.
Cursor agent calls 'list' at task start to check for waiting messages.
Cursor agent calls 'read' for detail, then 'ack' when handled.
Periodic 'purge' to clean old acked messages.
No daemon, no network — pure filesystem. Default dir: ~/.cursor-mcp/inbox/ Override with CURSOR_INBOX_DIR env var.
Inputs: operation (required), sender, subject, body, +7 more. Returns: object
cursor_sdkA
Fleet-curated @cursor/sdk / cursor-sdk guidance (read-only, no agent spawn).
Jun 2026 SDK release: custom tools, auto-review, JSONL stores, nested subagents. Use before writing new headless automation — complements cursor_docs topics.
Inputs: operation (required). Returns: object
cursor_usageA
Cursor billing and spend guardrails (read-only).
Requires CURSOR_API_KEY. Admin endpoints also accept CURSOR_ADMIN_API_KEY (crsr_ team key). Use alert_check on a schedule (e.g. Fritz every 2h) instead of manual dashboard checks.
Inputs: operation (required), hours, email. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct domain: cloud agents, documentation, help, inter-agent inbox, SDK guidance, and billing. No overlap in purpose, clear boundaries.
All tools follow a consistent 'cursor_<noun>' pattern with lowercase snake_case, making them easily predictable and grouped.
Six tools is well-scoped for the server's purpose, covering key Cursor ecosystem areas without being too sparse or bloated.
Covers cloud agent inspection, documentation, help, inbox messaging, SDK guidance, and billing. Minor gap: cloud agent management lacks create/delete, but this is likely intentional.
Maintenance
Related MCP Connectors
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that instruments Cursor AI agent interactions with OpenTelemetry traces and logs to monitor agent turns and performance. It enables tracking of user queries, assistant responses, and tool usage through GenAI-compliant telemetry spans.MIT
- AlicenseAqualityDmaintenanceMCP server that wraps Cursor Enterprise API to enable AI agents to answer questions about team spending, usage, and model adoption.1719 npm1MIT
- AlicenseAqualityCmaintenanceMCP server exposing Cursor's HTTP APIs for managing Cloud Agents, Team/Org Admin, Analytics, Bugbot, AI Code Tracking, and Fleet with read-only and read-write modes.61MIT
- AlicenseBqualityDmaintenanceA fast, hardened MCP server that lets any MCP host drive the Cursor Agent CLI for heavy repo-aware tasks like search, analysis, planning, and edits, keeping host context small and token costs low.101MIT