cursor-dispatcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURSOR_API_KEY | No | Cursor agent API key for authentication (bypasses login). | |
| CURSOR_HARNESS_BIN | No | Path to cursor-agent binary. | cursor-agent |
| CURSOR_HARNESS_HOME | No | Root data directory for run history. | ~/.claude-cursor-harness |
| CURSOR_HARNESS_MODELS | No | Comma-separated list of allowed models. | |
| CURSOR_HARNESS_SANDBOX | No | Sandbox mode setting. | |
| CURSOR_HARNESS_CWD_ROOT | No | Root working directory for subagents. | ~/workspace |
| CURSOR_HARNESS_MAX_RUNS | No | Maximum number of runs to keep. | 200 |
| CURSOR_HARNESS_MAX_AGE_DAYS | No | Maximum age in days before deletion. | 14 |
| CURSOR_HARNESS_DEFAULT_MODEL | No | Default model for subagents. | |
| CURSOR_HARNESS_PRUNE_ON_SPAWN | No | Prune on each spawn. | true |
| CURSOR_HARNESS_PRUNE_ON_STARTUP | No | Prune on startup. | true |
| CURSOR_HARNESS_COMPRESS_AFTER_DAYS | No | Days after which to compress events. | 7 |
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 | {} |
| logging | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spawn_subagentA | Launch a Cursor subagent with the given prompt. Returns immediately with a run_id; the subagent runs asynchronously. Model must be in the allowlist. Use get_subagent_events or subscribe to subagent:///events to observe progress. |
| send_subagent_messageA | Send a follow-up message to a running subagent (resumes the same chat). Errors if a turn is already in flight. |
| get_subagent_statusB | Return the current status of a subagent run. |
| get_subagent_eventsA | Fetch NDJSON events emitted by a subagent since a given event id. Use for polling or to catch up after a notifications/resources/updated ping. |
| list_subagentsB | List subagent runs known to this harness. |
| cancel_subagentA | Terminate a running subagent (SIGTERM). |
| get_subagent_resultA | Return the final structured completion payload for a terminated run (status ∈ {completed, failed, cancelled, timed_out}). |
| prune_subagentsA | Compress / delete old terminal runs. By default follows the retention config (compress after N days, delete after M days, LRU cap). Pass overrides to run a manual cleanup or set dry_run=true to preview what would happen. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ppetko98/cursor-dispatcher'
If you have feedback or need assistance with the MCP directory API, please join our Discord server