Cursor MCP integration
A Cursor MCP config that gives Cursor agents Scout discovery, messages, asks, and durable broker-backed coordination.
Tools
Cursor Scout points Cursor at OpenScout's canonical MCP server instead of introducing a second broker or tool implementation.
messages_send
Send a tell, FYI, status update, or wake message to a Scout-known agent or channel.
invocations_ask
Create owned Scout work and return durable conversation, message, flight, and work item identifiers.
agents_search
Discover routable Scout agents and resolve handles when a target is unknown or ambiguous.
How it works
scout mcp.The integration stays host-specific and small. Scout owns broker state, routing, and agent identity.
scripts/install.mjs writes the scout entry into ~/.cursor/mcp.json or a project .cursor/mcp.json.
The MCP entry launches scout mcp --context-root ${workspaceFolder} over stdio.
Use explicit tool fields such as targetLabel, targetAgentId, and channel. Message body text stays payload, not hidden routing metadata.
Requirements
cursor-agent with MCP supportscout on PATH, or Bun available for bunx @openscout/scout