Install in Cursor
Cursor ships with MCP support behind Settings → Features → Model Context Protocol. This guide covers the current Cursor 1.x config format.
Prerequisites
- Cursor 1.0+ (MCP support). Older builds need to upgrade.
- Node.js 18+ on PATH.
- PlanMySaaS API key from Settings → API Keys.
Step 1 — Open Cursor MCP settings
- Cursor → Settings (⌘, on macOS, Ctrl+, on Windows/Linux).
- Under Features, find Model Context Protocol.
- Click Edit in config.json.
Step 2 — Paste the PlanMySaaS block
{
"mcpServers": {
"planmysaas": {
"command": "npx",
"args": ["-y", "@planmysaas/mcp-server"],
"env": {
"PLANMYSAAS_API_KEY": "pms_live_paste_your_key_here"
}
}
}
}Step 3 — Restart Cursor
Fully quit and reopen. The MCP dot indicator in the chat pane should turn green for PlanMySaaS within a few seconds.
Step 4 — Try it
Open the chat pane (⌘L), switch to Agent mode (tools-enabled), and prompt:
Use PlanMySaaS to plan me a no-code invoice OCR SaaS. Give me architecture + features.
Cursor will show tool-call cards for generate_architecture and generate_features before replying with a summary.
Scope configuration
If you created a readonly key, generation endpoints will return 403. For a full dev workflow, generate a full-scope key. Keep a separate readonly key for status checks in CI.
Project-level keys
Cursor also supports per-project MCP config at .cursor/mcp.json. Same block as above — useful when a specific repo should use a specific workspace's credits:
# .cursor/mcp.json (project root)
{
"mcpServers": {
"planmysaas": {
"command": "npx",
"args": ["-y", "@planmysaas/mcp-server"],
"env": { "PLANMYSAAS_API_KEY": "pms_live_…" }
}
}
}Gitignore this file (.cursor/mcp.json) — never commit the key.
Troubleshooting
Tools missing?
- Toggle Cursor's MCP setting off and on to reload.
- Check Cursor's output panel (View → Output → Cursor MCP) for handshake errors.
- Run
npx -y @planmysaas/mcp-serverin a terminal — it should announce the server name.
See also Claude Desktop install or the full API docs.