cursor-sdk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURSOR_API_KEY | Yes | Your Cursor API key. Create one at the Cursor Dashboard → API Keys (user key) or Team settings (service account key). | |
| CURSOR_MCP_DEFAULT_MODEL | No | Optional default model id used when a tool call omits one. Default is 'auto'. | auto |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cursor_whoamiA | Verify the configured Cursor API key and return the authenticated account identity. Use this first to confirm authentication works before running an agent. |
| cursor_list_modelsA | List the Cursor models available to the configured account. Use the returned ids as the |
| cursor_run_agentA | Run a Cursor Agent (local runtime) against a working directory and return the final result. The agent can read, edit, and write files and run shell commands in |
| cursor_follow_upA | Continue an existing Cursor Agent conversation by |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: authentication, model listing, starting an agent, and continuing a conversation. No overlap.
All tools use snake_case with a consistent 'cursor_' prefix and action-oriented verbs, forming a predictable pattern.
With 4 tools, the set covers the essential interactions (auth, model list, run, follow-up) without bloat or gaps.
The domain is well-covered for basic usage; missing an optional stop/status tool, but core workflows are complete.