EchoPMDevelopers

Claude Desktop & Windsurf

Beta

Connect Claude Desktop or Windsurf to EchoPM portfolio MCP.

Both clients use the same org MCP key and HTTP endpoint as Cursor.

Claude Desktop#

Uses mcp-remote to bridge Streamable HTTP + Bearer header:

{
  "mcpServers": {
    "echopm": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.echopm.app/api/mcp",
        "--header",
        "Authorization: Bearer YOUR_MCP_KEY"
      ]
    }
  }
}

Config file (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json

The manager MCP connect wizard generates this JSON when you select Claude Desktop.

Windsurf#

Windsurf uses the same Streamable HTTP JSON shape as Cursor:

{
  "mcpServers": {
    "echopm": {
      "url": "https://mcp.echopm.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      }
    }
  }
}

Add via Windsurf MCP settings (see their docs for config file location).

Local development#

  1. Run pnpm dev:agents-http (default port 3010)
  2. In the wizard, choose Local environment → http://localhost:3010/api/mcp
  3. Use your org MCP test key

Tool discovery#

After connecting, ask your client to list tools — you should see all portfolio tools. If tools are missing, verify the key type is MCP (not REST-only) and the Bearer header is set.