Connecting

Pick your client below. Each connects to the Slothbox MCP server at https://mcp.slothbox.dev.

Claude (claude.ai)

Open Settings → Connectors, click Add custom connector, and paste in the server URL:

https://mcp.slothbox.dev

Sign in to Slothbox when the popup appears. The tools become available in any conversation.

Claude Code (CLI)

Run this in your terminal:

claude mcp add --transport http slothbox https://mcp.slothbox.dev

The first time you invoke a Slothbox tool, Claude Code opens a browser to sign you in.

Claude Desktop

Claude Desktop expects local servers, so use the mcp-remote bridge. Add this block to your claude_desktop_config.json and restart Claude Desktop:

{
  "mcpServers": {
    "slothbox": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.slothbox.dev"]
    }
  }
}

The first run opens a browser to sign in; after that the connection is silent.

Cursor

Add Slothbox to your ~/.cursor/mcp.json (create the file if it doesn't exist):

{
  "mcpServers": {
    "slothbox": {
      "url": "https://mcp.slothbox.dev"
    }
  }
}

Cursor will prompt you to sign in the first time you use a Slothbox tool.

Codex CLI

Run this in your terminal:

codex mcp add slothbox --url https://mcp.slothbox.dev

Codex opens a browser the first time a Slothbox tool is invoked.

Other clients

Any client that supports remote MCP servers with OAuth should work. Give it the URL above and follow whatever sign-in flow it offers. If the client expects local stdio servers, wrap the URL with mcp-remote the same way the Claude Desktop example does:

npx mcp-remote https://mcp.slothbox.dev