Skip to main content

​
Quick start

PARSEC_API_KEY=pk_live_... npx parsec-mcp serve
Get your API key at parsecapi.com.
The current Parsec MCP server uses a local stdio transport. It works well with desktop and CLI MCP clients that launch a local process. It is not yet documented here as a hosted remote MCP server over HTTP or SSE.

​
Environment variables

VariableRequiredDescription
PARSEC_API_KEYYesYour Parsec API key
PARSEC_API_BASE_URLNoOverride API base URL. Default: https://api.parsecapi.com
PARSEC_DISABLE_WALLET_EXPORTNoSet to 1 to disable the wallet export tool
PARSEC_MCP_ENABLE_RAWNoSet to 1 to enable the advanced raw API escape hatch

​
Supported clients

ClientSupported hereSetup style
Claude DesktopYeslocal stdio config file
Claude CodeYesclaude mcp add
CursorYes.cursor/mcp.json
VS Code / CopilotYes.vscode/mcp.json
Windsurf / ClineYesMCP config JSON
CodexYescodex mcp add
ChatGPT hosted connectorsNot yetrequires remote MCP transport

​
Codex

Add Parsec as a global MCP server: 
codex mcp add --env PARSEC_API_KEY=pk_live_... parsec -- npx -y parsec-mcp serve
Then verify it appears: 
codex mcp list

​
Claude Code

Add Parsec to the current project: 
claude mcp add -s project -e PARSEC_API_KEY=pk_live_... parsec -- npx -y parsec-mcp serve
This writes a local .mcp.json entry for the project.

​
JSON config clients

These clients all launch the same local stdio command. The only difference is where the JSON lives and whether the top-level key is mcpServers or servers.
ClientConfig fileTop-level key
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonmcpServers
Cursor.cursor/mcp.jsonmcpServers
VS Code / Copilot.vscode/mcp.jsonservers
Windsurf / Clineyour MCP config JSONmcpServers
Use this shape for Claude Desktop, Cursor, Windsurf, and Cline: 
{
  "mcpServers": {
    "parsec": {
      "command": "npx",
      "args": ["-y", "parsec-mcp", "serve"],
      "env": {
        "PARSEC_API_KEY": "pk_live_..."
      }
    }
  }
}
For VS Code / Copilot, use the same block under servers instead: 
{
  "servers": {
    "parsec": {
      "command": "npx",
      "args": ["-y", "parsec-mcp", "serve"],
      "env": {
        "PARSEC_API_KEY": "pk_live_..."
      }
    }
  }
}

​
Verify the server is working

Once the server is connected in your client, try a simple read-only prompt:
  • “What prediction markets are available about Bitcoin?”
  • “Am I set up to trade?”
  • “Show me the orderbook for the top Bitcoin market”
If the tools do not appear, restart the MCP client and confirm that npx parsec-mcp serve runs successfully in a terminal. If you need a safer first pass, stay on read-only tools before using any live trading tool. See Trading & Safety.