Cursor MCP setup — PickWise

Where to configure

Config file locations

macOS / Linux	`~/.cursor/mcp.json`
Windows	`%USERPROFILE%\.cursor\mcp.json`

Steps

Good setup flow

Get your workspace API key and confirm your PickWise login email with your admin.
Open or create ~/.cursor/mcp.json in your home directory.
Add the pickwise server block (see template below). Use your real key and email — never placeholders.
Save the file, fully quit Cursor, and reopen the project.
In Settings → MCP, confirm pickwise is connected. Paste your published task prompt into agent chat.

Cursor-specific notes

Cursor merges global and project MCP config — prefer the global file for one setup across repos.
If you use multiple MCP servers, keep pickwise as a distinct key inside mcpServers.

Template

{
  "mcpServers": {
    "pickwise": {
      "url": "https://mcp.pickwise.dev/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>",
        "X-Pickwise-Client-Id": "<your-work-email>"
      }
    }
  }
}

Example (replace with your values)

{
  "mcpServers": {
    "pickwise": {
      "url": "https://mcp.pickwise.dev/mcp",
      "headers": {
        "Authorization": "Bearer pw_live_7f3a9c2e1b4d8f6a0c5e",
        "X-Pickwise-Client-Id": "jane@yourcompany.com"
      }
    }
  }
}

Good setup checklist

Sign in and create API keys at https://intelligence.pickwise.dev/api-keys — not from chat or task prompts.
MCP endpoint in IDE config is exactly https://mcp.pickwise.dev/mcp over HTTPS (not the setup guide URL).
Authorization uses Bearer <api-key>; X-Pickwise-Client-Id is the same email you use on the portal.
PickWise MCP tools appear in the IDE after a full restart (not just reload window).
Your task standard is published before developers begin work in the IDE (pickwise_begin_task).

Troubleshooting

Common things to debug

Most connection issues are config path, JSON/TOML syntax, or credentials — not PickWise itself.

What you see	Likely cause	What to try
401 Unauthorized or authentication failed	Wrong API key, revoked key, or email header does not match your PickWise account.	Create a fresh key at https://intelligence.pickwise.dev/api-keys. Copy the full pw_live_… value once. Match X-Pickwise-Client-Id to your portal login email exactly.
PickWise tools never appear in the assistant	Config file path is wrong, JSON is invalid, or the IDE was not restarted after editing.	Validate JSON (trailing commas break parsers). Save the file, quit the IDE completely, reopen, and check the MCP server list.
Connection error or timeout	Corporate proxy, offline VPN, or typo in the URL.	Confirm https://mcp.pickwise.dev/mcp is reachable from your machine. Try curl with the same headers if your security team allows it.
Agent runs but policy decisions are not logged	Task prompt missing, standard not published, or a different MCP server is active.	Ensure the task standard is published and the developer uses pickwise_begin_task (or pickwise_load_standard with the standard ID). Ensure only one pickwise entry exists in mcpServers.

Other IDEs

Using a different client?

VS Code Windsurf Claude Desktop OpenAI Codex JetBrains IDEs