Skip to main content
Glama
lipey1

Cursor Agent MCP

by lipey1

cursor_agent_run

Execute a one-off prompt via the Cursor agent CLI for heavy repo-aware tasks like search, analysis, planning, and edits.

Instructions

Legacy single-shot chat (prompt as positional). Prefer cursor_agent_chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNo
forceNoPass --force / --yolo so the agent can run shell without prompts. Env: CURSOR_AGENT_FORCE.
modelNoModel id for the CLI (e.g. auto, gpt-5, composer-2). Overrides CURSOR_AGENT_MODEL.
trustNoPass --trust (default true). Env: CURSOR_AGENT_TRUST.
promptYes
api_keyNoCursor API key (crsr_…). Prefer CURSOR_API_KEY / CURSOR_AGENT_API_KEY in MCP env.
config_dirNoExplicit CURSOR_CONFIG_DIR override. Implies isolated config for this call.
executableNo
extra_argsNo
bare_configNoUse an isolated CURSOR_CONFIG_DIR (~/.cursor-agent-mcp by default) so the CLI does not load user MCPs/plugins. Much faster startup. Env: CURSOR_AGENT_BARE_CONFIG=1.
echo_promptNo
output_formatNotext
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It only labels as 'legacy' and 'single-shot chat', with no details on side effects, permissions, or call behavior. This is insufficient for a tool with 12 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is very short (two sentences), which is concise but may be under-specified given the tool's complexity. It front-loads the key information (legacy, prefer alternative) but lacks structure for the many parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters, no annotations, no output schema, and high complexity, the description is severely incomplete. It does not cover return values, error conditions, or behavior beyond being a 'single-shot chat'. Agent cannot fully understand the tool's capabilities.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, meaning half of parameters have descriptions. The description adds no parameter info beyond the schema, failing to compensate for the undocumented parameters. Agent gets no additional meaning from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it is a 'legacy single-shot chat' with positional prompt, distinguishing it from sibling cursor_agent_chat. The verb 'chat' and resource specification are clear, though it could be more explicit about the exact function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly directs preference to cursor_agent_chat, providing clear guidance on when not to use this tool. Lacks explicit context on when this legacy tool should still be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/lipey1/cursor-agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server