Cursor

Cursor runs the MCP server as a per-project subprocess, so each project you open can have its own Debriefer config.

Install

{  "mcpServers": {    "debriefer": {      "command": "npx",      "args": [        "@debriefer/mcp-server"      ],      "env": {        "DEBRIEFER_API_KEY": "sk_live_..."      }    }  }}

Verify it's connected

Open the command palette with Cmd/Ctrl+Shift+P and run MCP: List Servers. You should see debriefer in Cursor's MCP servers panel with an active status. If it isn't there, see Troubleshooting.

Try a prompt

Client-specific notes

• Per-project config: Cursor reads .cursor/mcp.json from the project root — there's no global file. Commit a redacted version to share the setup with your team, but keep the API key in a local-only file or environment variable.
• Reloading: After editing .cursor/mcp.json, run Reload Window from the command palette. Cursor doesn't hot-reload MCP servers.
• Tool calls in chat: Cursor surfaces each tool call inline in the chat panel — expand a call to see the arguments and the raw response. Useful when you want to confirm the agent picked the right blueprint or workspace.
• Logs: MCP server stderr appears in Cursor's developer console (Help → Toggle Developer Tools → Console). Filter for debriefer to isolate Debriefer output from other servers.
• Per-project keys: Because the config is local to the project, you can scope different API keys to different repos — handy if you're working across multiple Debriefer organizations.