Connect AI assistants (Claude Code, Antigravity, Cursor, …) to this site: search the docs, inspect any ledger address and prepare transaction manifests through the Model Context Protocol.
Streamable HTTP MCP server, stateless and without authentication. Any MCP-compatible AI client can connect to this URL.
/api/mcpChoose your client and copy its configuration. The server is registered under the name "radix".
Run this command in your terminal, then restart the session.
$ claude mcp add --transport http radix /api/mcpThis server prepares and previews transactions but cannot sign them. Install the local connector to pair your Radix Wallet and sign — your private key never leaves your phone.
Signing needs a live channel to your phone, which a stateless web server can't hold. So a small local MCP server, radix-connector-mcp, does it: it opens the Radix Connect channel and your phone approves. Install it once and both servers work together.
Option A · with a Rust toolchain (any OS)
$ cargo install --git https://github.com/genkipool/radixdlt-rust-sdk radixdlt-connector-mcpOption B · prebuilt binary (no Rust needed - recommended option)
$ curl -fsSL https://raw.githubusercontent.com/genkipool/radixdlt-rust-sdk/main/scripts/install-connector.sh | sh> irm https://raw.githubusercontent.com/genkipool/radixdlt-rust-sdk/main/scripts/install-connector.ps1 | iexThe local connector is registered under the name "radix-connector". If the binary is not on your PATH, use its absolute path as the command. Reload the client once so the new tools appear.
Claude Code
$ claude mcp add radix-connector -- radix-connector-mcpOther clients · JSON config
{
"mcpServers": {
"radix-connector": {
"command": "radix-connector-mcp"
}
}
}The phone signs every action (you always approve there). The connector only stores the channel password locally; the private key and the QR never leave your machine.
ALERT: AI can hallucinate and generate unsolicited transactions. Carefully examine the transaction on your phone before signing, and always run preliminary tests on stokenet.
A SKILL.md generated from the live tool registry: connection info, every tool with its parameters, and recommended workflows. Give it to your AI agent so it masters this server.
Once connected, ask your AI assistant things like these. Click a question to copy it.
Every ledger and console tool accepts an optional "network" parameter ("mainnet" or "stokenet") that defaults to mainnet. Just mention the network in your question — "list the validators on stokenet" — and the AI fills the parameter for you. Addresses also carry their network in the prefix: mainnet uses …rdx1 (account_rdx1…) and stokenet uses …tdx_2_1 (account_tdx_2_1…), so the AI can detect the right network with the inspect_address tool and will never mix networks in one transaction.
Real response of this server's tools/list method — what your AI will see.
❯ POST /api/mcp { "method": "tools/list" }
Querying /api/mcp …
Tool names and descriptions are intentionally shown in English: this block is the exact live response that AI clients receive, and English specifications maximise tool-selection accuracy across models. The assistant still answers you in your language.