cursor-agents-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURSOR_API_KEY | No | A non-expiring Cursor API key from the Cursor dashboard. An alternative to authenticating the SDK via Cursor.auth.login(), which mints a key into ~/.cursor/sdk/auth.json. | |
| CURSOR_AGENTS_STATE_ROOT | No | Overrides the directory where state (including agent transcripts) is stored. | ~/.cursor-agents-mcp/ |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spawnA | Delegate a task to a Cursor agent (Grok by default) running detached in the background. Returns immediately with an agent id — it does NOT wait. The agent shares none of your context, so |
| follow_upA | Send another turn to an existing agent, keeping its full conversation. Use this instead of spawning a fresh agent whenever the work builds on what that agent already did — it keeps the context and costs far less. The agent must have finished; use steer for a live run. |
| listB | List agents with their state, elapsed time, cost and latest activity. One line each. |
| inspectA | Show what one agent has done, as a compact digest — one line per tool call, not a transcript. Pass the |
| waitA | Block until the named agents finish. This blocks YOUR whole turn, so prefer the background-task bridge from spawn — use this only when there is genuinely nothing else to do. On timeout it returns progress rather than nothing. |
| steerA | Inject a message into an agent's turn while it is still running, without killing its work. Use this to correct course mid-run — it is strictly better than stopping and re-prompting. |
| stopA | Cancel an agent's current run. The agent stays resumable via follow_up. |
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 7 tools
Each tool targets a clearly distinct action in the agent lifecycle. spawn creates, follow_up resumes finished agents, steer injects into live runs, stop cancels, list/inspect/wait provide distinct status, detail, and blocking behaviors. Descriptions explicitly disambiguate edge cases.
All tool names are lowercase snake_case and follow a consistent imperative verb style (spawn, follow_up, steer, stop, list, inspect, wait). The single multi-word name follow_up adheres to the same convention.
Seven tools precisely cover the core agent orchestration lifecycle without bloat. Each tool has a clear purpose and there are no redundant or missing operations for the stated scope.
The set covers spawn, monitor, interact, and stop comprehensively. Minor gap: there is no direct tool to retrieve an agent's final result or transcript as a first-class output—inspect provides a digest and directs users to shell tools, which is a small workaround.