← Registry

API Tools

bitrouter.ai

Provides access to BitRouter's documentation and model routing information, including pricing and configuration snippets.

1 endpoint3 known toolsFirst detected August 16, 2026Last detected August 16, 2026

ENDPOINT 1

https://bitrouter.ai/mcp

No auth detected

MCP server metadata

Name
bitrouter-docs
Version
1.0.0
Capabilities
tools.listChangedresources.listChanged
Server instructions

BitRouter documentation server (public, no auth). Use search_docs to find guides, get_doc to read a page, and lookup_model to check model availability and config.

Known tools 3

search_docs

Full-text search over BitRouter's documentation.

Inferred read-only
get_doc

Fetch one documentation page as Markdown.

Inferred read-only
lookup_model

Check whether a model is routable through BitRouter and get its pricing, context window, and a copy-paste config snippet.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bitrouter-docs]
url = "https://bitrouter.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "bitrouter-docs": {
      "type": "http",
      "url": "https://bitrouter.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: bitrouter-docs
Remote MCP URL: https://bitrouter.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bitrouter-docs": {
      "url": "https://bitrouter.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "bitrouter-docs": {
      "type": "http",
      "url": "https://bitrouter.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "bitrouter-docs",
  "transport": "streamable-http",
  "url": "https://bitrouter.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.