Setup: Claude Desktop

​

Prerequisites

• Claude Desktop installed
• A ProBeya API key (generate from Settings > API Keys in the ProBeya web app)
• Node.js 18+ installed locally
• The ProBeya MCP server built (apps/mcp/dist/index.js)

​

Step 1: Locate the Config File

Claude Desktop reads MCP server configuration from claude_desktop_config.json. The file location depends on your operating system:

• macOS
• Windows
• Linux

~/Library/Application Support/Claude/claude_desktop_config.json

If the file does not exist, create it.

​

Step 2: Add the ProBeya MCP Server

Add the probeya entry to the mcpServers object in your config file:

{
  "mcpServers": {
    "probeya": {
      "command": "node",
      "args": ["/path/to/probeya/apps/mcp/dist/index.js"],
      "env": {
        "PRPROBEYA_API_KEY": "probeya_sk_live_...",
        "DATABASE_URL": "postgresql://user:pass@host:5432/probeya"
      }
    }
  }
}

​

Using npx (no local clone needed)

If the MCP server is published as an npm package:

{
  "mcpServers": {
    "probeya": {
      "command": "npx",
      "args": ["@probeya/mcp"],
      "env": {
        "PRPROBEYA_API_KEY": "probeya_sk_live_..."
      }
    }
  }
}

​

Step 3: Restart Claude Desktop

After saving the config file, fully quit and relaunch Claude Desktop. The MCP server will start automatically as a child process.

​

Step 4: Verify the Connection

In Claude Desktop, you should see the ProBeya tools available in the tool picker. Try a simple query to verify:

“List my workspaces in ProBeya”

Claude should call the list_workspaces tool and return your organization’s workspace hierarchy.

You can also check the server logs in Claude Desktop’s developer console. On startup, the server outputs:

[MCP] Authenticating...
[MCP] Jane Smith ([email protected]) -- org org_abc123
[MCP] Scopes: full access
[MCP] ProBeya MCP server v2.0.0 ready (stdio)

​

Troubleshooting

​

Security Notes

• The API key is passed via the env configuration, not as a command-line argument, to prevent leakage in process listings
• The MCP server runs locally as a child process of Claude Desktop — your data flows directly between the local process and the database
• Failed authentication causes the server to exit immediately, preventing any unauthenticated tool calls
• The API key is never logged, even in debug mode