Setup Guide

Complete instructions for connecting BotKelp to your AI platform. Choose your setup based on whether you need custom credentials (for private repos) or just want to browse components.

Quick start (no credentials)

Browse components and generate with public/shared scaffolds. No GitHub credentials needed.

Claude.ai

Go to claude.ai → Customize → Connectors
Click "Add custom connector"
Name: botkelp, URL: https://www.botkelp.com/mcp
Leave OAuth Client ID/Secret blank (BotKelp hosts MCP OAuth 2.1), click Add, complete consent if prompted
Start a new chat and use the MCP

Claude Desktop

For local development with custom GitHub credentials.

~/.claude/claude_desktop_config.json

{
  "mcpServers": {
    "botkelp": {
      "command": "npx",
      "args": ["mcp-remote", "https://www.botkelp.com/mcp"]
    }
  }
}

To get your API key:

Sign in at botkelp.com/login
Go to the Dashboard and create an API key
Complete MCP OAuth (or send Authorization: Bearer bk_live_…). Never pass the key as a tool argument — call get_account_status to confirm it is linked
Reload Claude Desktop and start using purchase_scaffold

Claude Code (Web)

Add the BotKelp MCP server via the Claude.ai connectors page.

Go to claude.ai → Settings → Connectors
Click "Add custom connector"
Set the URL to https://www.botkelp.com/mcp
Leave authentication blank and save

Mistral Vibe

Uses install.json to handle credentials automatically.

Add the MCP server

vibe mcp add botkelp --url https://www.botkelp.com/mcp

✓ Vibe stores the connection and automatically passes it to the MCP on each run. No manual setup needed after this.

Cursor / Windsurf

Add BotKelp as a remote MCP server in your config.

~/.cursor/mcp.json (Cursor) or ~/.codeium/windsurf/mcp_config.json (Windsurf)

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

Troubleshooting

MCP doesn't connect

Ensure the server URL is correct and your client supports HTTP/SSE MCP transport:

Claude Desktop: requires mcp-remote or a client that supports HTTP transport
Claude Code (web): native HTTP MCP support via Connectors
Cursor / Windsurf: use the url key, not command

purchase_scaffold says insufficient credits

Add credits from the Dashboard or pay per-call in USDC via the Pay page.

No credentials needed

If you only want to browse/search components and don't plan to generate:

Use the hosted HTTP URL (no local setup needed)
get_help and get_component work unauthenticated
purchase_scaffold requires an API key or x402 payment

Still stuck? Contact us.