MCP Clients

Fp Switchboard works with any MCP-compatible client. This guide covers the most popular options.

Claude Desktop

Claude Desktop has native MCP support and is the recommended client.

1. Open Claude Desktop settings

   Click the Claude menu → Settings → Developer

2. Edit the MCP configuration

   Click “Edit Config” to open claude_desktop_config.json

3. Add Fp Switchboard

   {
     "mcpServers": {
       "fp-switchboard": {
         "url": "https://api.switchboard.fpdigital.ai/mcp/unified",
         "headers": {
           "Authorization": "Bearer fps_unified_your_token_here"
         }
       }
     }
   }

4. Restart Claude Desktop

Tip

Replace fps_unified_your_token_here with your actual token from the Fp Switchboard dashboard.

Cursor

Cursor IDE supports MCP through its AI settings.

1. Open Cursor settings

   Cmd+, (Mac) or Ctrl+, (Windows/Linux)

2. Navigate to AI → MCP Servers

3. Add a new server

   • Name: fp-switchboard
   • URL: https://api.switchboard.fpdigital.ai/mcp/unified
   • Headers: Authorization: Bearer fps_unified_your_token_here

4. Save and restart Cursor

ChatGPT with MCP Bridge

ChatGPT doesn’t natively support MCP, but you can use the MCP Bridge.

Using npx

npx @anthropic/mcp-bridge \
  --server https://api.switchboard.fpdigital.ai/mcp/unified \
  --auth "Bearer fps_unified_your_token"

Using Docker

docker run -e MCP_SERVER=https://api.switchboard.fpdigital.ai/mcp/unified \
  -e MCP_AUTH="Bearer fps_unified_your_token" \
  ghcr.io/anthropic/mcp-bridge

Other MCP Clients

Any client that supports the MCP protocol can connect to Fp Switchboard:

Client	Configuration
VS Code Copilot	Coming soon
Windsurf	MCP settings in preferences
Custom Apps	Use the MCP SDK with our endpoint

Per-Service Tokens

If you only want specific tools available, use per-service tokens instead of unified:

{
  "mcpServers": {
    "google": {
      "url": "https://api.switchboard.fpdigital.ai/mcp/google",
      "headers": {
        "Authorization": "Bearer fps_google_your_token"
      }
    },
    "slack": {
      "url": "https://api.switchboard.fpdigital.ai/mcp/slack",
      "headers": {
        "Authorization": "Bearer fps_slack_your_token"
      }
    }
  }
}

Using Custom Bundles

If you’ve created a custom bundle, use the bundle endpoint:

{
  "mcpServers": {
    "my-bundle": {
      "url": "https://api.switchboard.fpdigital.ai/mcp/bundle/my-bundle-id",
      "headers": {
        "Authorization": "Bearer fps_bundle_your_token"
      }
    }
  }
}

Troubleshooting

”Connection refused”

• Verify your token is correct (no extra spaces or characters)
• Check that the URL is exactly as shown above
• Ensure your network allows HTTPS connections

”Unauthorized”

• Your token may have expired—generate a new one from the dashboard
• Make sure you’re using the correct token type for the endpoint

Tools not appearing

• Restart your MCP client after configuration changes
• Check the dashboard to ensure you have connected services
• Verify the token has access to the services you expect

Security Best Practices

1. Never share your tokens in public repositories or chat logs
2. Use environment variables when possible instead of hardcoding tokens
3. Rotate tokens regularly from the dashboard
4. Use per-service tokens if you only need access to specific services