Clusterfudge via MCP

All of the functionality available via the Clusterfudge API can be exposed to agentic systems via MCP.

You can configure agents to access these tools over HTTP (remote MCP) or locally over stdio (local MCP).

Remote MCP via HTTP

Our MCP URL is https://clusterfudge.clusterfudge.com/mcp, so you should be able to add this value to any software that can be configured to add remote MCPs via URL. You may need to login (see the Authentication section below).

Here is how you can configure this in Cursor (Cmd+Shift+P, 'Open MCP Settings', 'New MCP Server', modify mcp.json):

{
  "mcpServers": {
    "clusterfudge": {
      "url": "https://clusterfudge.clusterfudge.com/mcp"
    },
  }
}

Authentication

Our MCP handlers accept both session IDs (which are issued via a standard browser-based oauth flow) and API keys (which are found in the Clusterfudge dashboard). Not all MCP clients support directly specifying a custom bearer token, check your software's MCP configuration docs to find out if this is an option for you.

Here is an example of directly specifying a Clusterfudge API key to interact with the Claude API (which supports adding custom bearer tokens):

curl https://api.anthropic.com/v1/messages \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $YOUR_ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: mcp-client-2025-04-04" \
  -d '{
    "model": "claude-sonnet-4-20250514",
    "max_tokens": 1000,
    "messages": [{"role": "user", "content": "What tools do you have available?"}],
    "mcp_servers": [
      {
        "type": "url",
        "url": "https://clusterfudge.clusterfudge.com/mcp",
        "name": "clusterfudge",
        "authorization_token": "$YOUR_CF_API_TOKEN"
      }
    ]
  }'

Local MCP via clusterfudge-mcp

The clusterfudge-mcp is a standalone Model Context Protocol server that can be ran on the same system as your agent.

Download

Download our MCP server binary

curl https://get.clusterfudge.com/mcp.sh | sudo bash;

Once you have the binary installed, you can configure it in Cursor, Windsurf or Claude for Desktop by configuring the 'command' field in your config to point to the path you just installed our MCP binary to.

Here is an example of this as configured in Cursor:

{
  "mcpServers": {
    "clusterfudge-test": {
      "command": "/usr/local/bin/clusterfudge-mcp",
      "args": []
    },
  }
}