FlameWireDocs

Bittensor MCP

FlameWire's Bittensor MCP gives your coding assistant structured, Bittensor-specific context through one endpoint.

MCP Endpoint

https://bittensor-mcp.flamewire.io/mcp

Built-In RPC Context

The MCP server is already pinned to FlameWire's Bittensor RPC and can return _buildGuidance for implementation workflows.

Available Tools

  • get_chain_info
  • get_latest_block_summary
  • get_balance
  • get_account_info
  • get_subnet_info
  • get_delegates
  • call_rpc (read-only passthrough)

Editor Setup

Cursor

Create project-level .cursor/mcp.json or user-level ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bittensor": {
      "url": "https://bittensor-mcp.flamewire.io/mcp"
    }
  }
}

VS Code

Create .vscode/mcp.json:

{
  "servers": {
    "bittensor": {
      "type": "http",
      "url": "https://bittensor-mcp.flamewire.io/mcp"
    }
  }
}

Visual Studio

Add solution-level .mcp.json or global %USERPROFILE%/.mcp.json:

{
  "servers": {
    "bittensor": {
      "url": "https://bittensor-mcp.flamewire.io/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http bittensor https://bittensor-mcp.flamewire.io/mcp
claude mcp list
  1. Start with high-level tools like get_chain_info and get_subnet_info
  2. Use returned _buildGuidance to scaffold app structure
  3. Use direct RPC for production data paths
  4. Keep MCP config files in version control

Example Prompts

  • "Get chain info and runtime version from the Bittensor MCP."
  • "Get subnet info for netuid 1 and summarize key fields."
  • "Check balance for this address: <ss58-or-0x>."

Source

FlameWire - Bittensor MCP: One Server, Three Editors