MCP Server Setup

Give your agent direct access to Clawsmith data via the Model Context Protocol. Works with Claude Code, OpenClaw, Codex, Cursor, VS Code, Windsurf, and any MCP-capable client.

Step 1 - Get your API key

You need a Builder plan to use the MCP server. Once subscribed, create an API key at Settings → API Keys. It starts with clwsmth_ and is shown once.

Step 2 - Instant Setup

Paste this into Claude Code, OpenClaw, or any MCP-capable agent. It will configure the connection for you.

PROMPT

Connect to the Clawsmith MCP server at https://www.clwsmth.com/api/mcp using streamable HTTP transport. Add it with the name "clawsmith". Use this API key as a Bearer token in the Authorization header: clwsmth_YOUR_KEY_HERE

Replace clwsmth_YOUR_KEY_HERE with your actual API key. If your agent doesn't support auto-setup, use the manual steps below.

Step 3a - Claude Code

Pick one of the options below. You do not need all of them.

Local scope is the default and only affects the current project:

BASH

claude mcp add --transport http clawsmith https://www.clwsmth.com/api/mcp \
  --header "Authorization: Bearer clwsmth_YOUR_KEY"

User scope makes the server available across all Claude Code projects:

BASH

claude mcp add --transport http --scope user clawsmith https://www.clwsmth.com/api/mcp \
  --header "Authorization: Bearer clwsmth_YOUR_KEY"

Manual JSON uses the same structure. Put it in .mcp.json at the project root for project scope, or under the top-level mcpServers key in ~/.claude.json for user scope:

JSON

{
  "mcpServers": {
    "clawsmith": {
      "type": "http",
      "url": "https://www.clwsmth.com/api/mcp",
      "headers": {
        "Authorization": "Bearer clwsmth_YOUR_KEY"
      }
    }
  }
}

Step 3b - OpenClaw

Native MCP command:

BASH

openclaw mcp set clawsmith \
  --url https://www.clwsmth.com/api/mcp \
  --header "Authorization: Bearer clwsmth_YOUR_KEY"

If you use mcporter:

BASH

mcporter config add clawsmith \
  --transport http \
  --url https://www.clwsmth.com/api/mcp \
  --header "Authorization: Bearer clwsmth_YOUR_KEY"

Step 3c - Codex

Pick one of the options below. Recommended: use the environment variable flow.

Add this to .codex/config.toml for project scope or ~/.codex/config.toml for user scope:

TOML

[mcp_servers.clawsmith]
url = "https://www.clwsmth.com/api/mcp"
bearer_token_env_var = "CLAWSMITH_API_KEY"

Set CLAWSMITH_API_KEY in your shell profile:

BASH

export CLAWSMITH_API_KEY=clwsmth_YOUR_KEY

If you prefer a static header instead:

TOML

[mcp_servers.clawsmith]
url = "https://www.clwsmth.com/api/mcp"
http_headers = { Authorization = "Bearer clwsmth_YOUR_KEY" }

Step 3d - Cursor, VS Code & Windsurf

Cursor - Add to .cursor/mcp.json for project scope or ~/.cursor/mcp.json for global scope:

JSON

{
  "mcpServers": {
    "clawsmith": {
      "type": "streamable-http",
      "url": "https://www.clwsmth.com/api/mcp",
      "headers": {
        "Authorization": "Bearer clwsmth_YOUR_KEY"
      }
    }
  }
}

VS Code - Add to .vscode/mcp.json. The root key must be servers, and the prompt input keeps the API key out of the file:

JSON

{
  "servers": {
    "clawsmith": {
      "type": "http",
      "url": "https://www.clwsmth.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:clawsmith-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "clawsmith-key",
      "description": "Clawsmith API Key",
      "password": true
    }
  ]
}

Windsurf - Add to ~/.codeium/windsurf/mcp_config.json:

JSON

{
  "mcpServers": {
    "clawsmith": {
      "serverUrl": "https://www.clwsmth.com/api/mcp",
      "headers": {
        "Authorization": "Bearer clwsmth_YOUR_KEY"
      }
    }
  }
}

Step 4 - Start

Once connected, paste this into your agent to start:

PROMPT

Use Clawsmith to show me the top rising signals in the OpenClaw ecosystem right now. For the highest-scored one, pull the full product brief and tell me if it's worth building.

You should see Clawsmith tool calls in the response. If you get an auth error, double-check your API key from Settings → API Keys.

Need help?

See the full API Reference for all available tools and parameters.