Loading...
Loading
Loading
The Bittensor.ai MCP server lets an AI client look up Bittensor network data and prepare transactions for you to sign. This page covers the server URL, how to sign in and how to add it to Claude and other clients.
The server is at:
https://bittensor.ai/mcpIt focuses first on validators: it can check whether a hotkey is a validator on a subnet, explain what is missing and show what each step costs. It also reads accounts, subnets, staking and transactions.
The API behind it is described on the API page.
You connect by signing in with your bittensor.ai account. Add the server URL to your client and nothing else: the client opens bittensor.ai in your browser, you log in as usual and approve the connection on the consent screen. API keys are not accepted on this server.
MCP access is granted per account. If yours does not have it, the consent screen says “MCP access isn't enabled for your account” and no connection is made. To ask about access, email [email protected].
The client receives a token that only this MCP server accepts. It lasts 15 minutes and is refreshed automatically.
Open Settings, then Connectors, choose Add custom connector and paste https://bittensor.ai/mcp. Then sign in with bittensor.ai when asked.
claude mcp add --transport http bittensor https://bittensor.ai/mcpThen run /mcp in Claude Code and choose Authenticate.
Any MCP client that supports remote servers over streamable HTTP and OAuth sign-in can connect: give it https://bittensor.ai/mcp. The client discovers bittensor.ai as the authorization server and registers itself.
A client can only be sent back to an https address or a loopback address after sign-in. A client whose sign-in returns to a custom URL scheme (Cursor's cursor://, for example) cannot complete it.
Amounts come back as decimal strings named by unit: TAO, or the subnet's alpha.
The server never holds your keys and never signs or submits anything. For a change on the chain, it prepares the call: checked against the live chain, priced and described in plain English. A call the chain would certainly reject is refused up front with the failing checks.
You then sign the prepared call yourself, on the bittensor.ai signing page (bittensor.ai/sign/<token>), with a polkadot.js Apps link that has the call loaded, or with a btcli command.
Never give an AI client a seed phrase or a private key. Nothing here asks for one.
The consent screen lists the permissions the client asks for:
data:read: Read chain, subnet, validator and account data.transactions:prepare: Prepare transactions for you to sign. It cannot sign or submit them.billing:read: Read your usage, credits and membership.account:read: Read the wallets you verified on bittensor.ai for your portfolio. It also covers your profile, email and sign-in sessions.The connection acts for your personal organization, with its tier, quota and credits.