Copy page

MCP Server

Connecting

The server speaks HTTP transport at https://0bull.net/mcp and authenticates with OAuth. Every client below follows the same shape: you give it the URL, it discovers the OAuth endpoints, and a browser window asks you to authorize with your 0bull.net account. There is no token to copy or paste.

You authorize as yourself, so the tools only see the accounts and phones your own account can reach.

Claude Code

Code
claude mcp add --transport http 0bull https://0bull.net/mcp

Then, inside Claude Code:

Code
/mcp

Pick 0bull and authenticate. A browser opens for the OAuth flow. Once you approve, the 24 tools are available.

Add --scope user to make the server available across all your projects rather than only the current one (the default scope is local).

Claude Desktop

Edit your claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Code
{
  "mcpServers": {
    "0bull": {
      "type": "http",
      "url": "https://0bull.net/mcp"
    }
  }
}

Restart Claude Desktop. It will prompt you to authenticate on first use.

Cursor

Edit .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project):

Code
{
  "mcpServers": {
    "0bull": {
      "type": "http",
      "url": "https://0bull.net/mcp"
    }
  }
}

Cursor picks the server up and prompts for OAuth in Settings → MCP.

Codex

Code
codex mcp add 0bull --url https://0bull.net/mcp

Codex detects OAuth support and starts the flow itself:

Code
Added global MCP server '0bull'.
Detected OAuth support. Starting OAuth flow…
Authorize `0bull` by opening this URL in your browser: <url>

Open the URL and approve. There is no separate login command to run afterwards.

The server is written to ~/.codex/config.toml:

Code
[mcp_servers.0bull]
url = "https://0bull.net/mcp"

Run codex mcp list to check it. The Auth column tells you whether you are logged in. If authorization ever lapses, codex mcp login 0bull re-runs the flow without re-adding the server.

OpenCode

Add the server to opencode.json in your project root:

Code
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0bull": {
      "type": "remote",
      "url": "https://0bull.net/mcp",
      "enabled": true
    }
  }
}

type and url are all the server needs. OpenCode auto-detects OAuth and prompts you to authorize on first use. OpenCode also reads a global config file if you would rather have the server in every project; see its configuration docs for the location.

OpenClaw

Code
openclaw mcp add 0bull \
  --url https://0bull.net/mcp \
  --transport streamable-http
openclaw mcp login 0bull

openclaw mcp login opens the browser for authorization. You can also add the server from Settings → MCP, where Sign in runs the same flow.

Check it with openclaw mcp doctor 0bull --probe, which connects and lists the tools it found.

Verifying

Ask your client to list the tools. You should see 24, starting with list-accounts-tool. A quick end-to-end check that touches no phone:

List my posting accounts.

That calls list-accounts-tool, a synchronous read. It answers immediately and returns every platform merged: TikTok, Instagram and YouTube. If you get an empty list rather than an error, you are connected and authorized.

Troubleshooting

The browser never opens, or authorization fails. Check that you used the full https://0bull.net/mcp path, not the bare host. The trailing /mcp is what your client discovers the OAuth endpoints from. If the browser opens but authorization fails, sign in at 0bull.net first, then retry.

Tools return "not found" for records you know exist. That is scoping, not a bug: you are authenticated as a user without access to them. See scoping.

Calls start failing in bursts. The rate limit is 250/min, and 60/min for screen reads.