cursor-agent-sync-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_executeB | Execute one bounded coding task through cursor-agent CLI (synchronous, blocks until done) and return a compact JSON report with diff/status context. |
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 1 tool
With only a single tool, there is no possibility of overlap or misselection; cursor_execute has one clearly distinct purpose.
The lone tool follows a clean snake_case verb_noun pattern (cursor_execute), which is readable and predictable even without siblings to compare against.
A single tool is thin for a server whose purpose is syncing/executing coding tasks; basic operations like status polling or cancellation are absent, making the surface feel under-scoped.
Only a synchronous execute operation exists, with no way to query task status, cancel a running task, or list history, so an agent hitting a long-running or stuck task has no recourse.