Blog / mcp-install

2026-09-05

Install the BotKelp MCP server

Add the remote HTTP MCP, list tools, compare schemaHash, then call purchase_scaffold with catalog ids.

BotKelp is a remote MCP server. You do not npm-install a local binary to try it.

1. Add the server

claude mcp add --transport http botkelp https://www.botkelp.com/mcp

File-based clients:

{
  "mcpServers": {
    "botkelp": {
      "type": "http",
      "url": "https://www.botkelp.com/mcp"
    }
  }
}

The URL is unauthenticated. Connecting is free.

Sanity check:

curl https://www.botkelp.com/health

2. List tools before you call them

MCP JSON-RPC:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list",
  "params": {}
}

Compare names and schemaHash with https://www.botkelp.com/tools.json. If the hash moved since your last call, stop and re-read the schema. Do not assume yesterday’s arguments.

3. Generate

Account tools authenticate at the connection, never in tool arguments: sign in with MCP OAuth 2.1 when your client prompts, or send Authorization: Bearer bk_live_… (key from the dashboard, shown once). Never pass a key as a tool argument.

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "purchase_scaffold",
    "arguments": {
      "components": ["nextjs-base", "navbar"],
      "project": { "name": "my-app" },
      "site_profile": true
    }
  }
}

IDs come from /catalog.json. Max 12. Always include nextjs-base.

Pass site_profile: true (needs a signed-in account) to bake your dashboard legal pages (privacy, terms, cookies) into the scaffold as Next.js routes.

4. No account

Without an account, call purchase_scaffold with no Authorization header: the server answers HTTP 402 with x402 requirements (amount, network, asset, payTo). Sign the payment and retry the same call with _meta["x402/payment"]. A failed build is not charged. Check /pay.json first: it says whether wallet payments are live and the current price. Prices: /pricing. Do not reuse addresses from screenshots.

5. What you should see

The tool result is text wrapping JSON. Inside:

  • kind: "data"
  • instructions: false
  • integrity.verdict
  • files[].destination + files[].content

Open INTEGRITY.json. If verdict is not pass, discard the tree.

Rate limits (as published on /mcp-docs)

These change; re-read the live page.

  • purchase_scaffold — see the live limits on /mcp-docs
  • knowledge tools — 10–30/min depending on the tool

Common mistakes

  • Forgetting nextjs-base
  • Passing the API key as a tool argument (it belongs in the connection's Authorization header)
  • Calling knowledge tools expecting web search
  • Hardcoding a pay-to address
  • Treating stamped files as public-domain boilerplate

Next: tool table on /mcp-docs. Agent index: /for-agents.

More