> For the complete documentation index, see [llms.txt](https://docs.luganodes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luganodes.com/rpc/mcp-server.md). # MCP server Read-only blockchain tools for AI agents on Ethereum, Bitcoin and Tron *** ### Overview The Luganodes RPC MCP server gives AI agents read-only access to Ethereum Mainnet, Ethereum Beacon, Bitcoin and Tron. Connect it to any Model Context Protocol (MCP) client and ask questions in plain language, such as "Why is my Bitcoin transaction still pending?" * **Read-only.** No tool can sign, send or broadcast, and every tool is marked with MCP's `readOnlyHint` annotation. Simulations and estimates commit nothing. * **Purpose-built.** Tools validate inputs, cap outputs and decode amounts, transfers and fees. There is no raw RPC passthrough. * **Same key and plan as RPC.** Each call draws compute units (CU) from your plan and reports its cost as `cu_charged`. ### Supported networks | Chain | Network | Tools | Minimum plan | | ------------------ | ------- | ----- | ------------ | | Ethereum Mainnet | Mainnet | 18 | Free | | Ethereum Beacon | Mainnet | 7 | Growth | | Bitcoin | Mainnet | 12 | Free | | Tron | Mainnet | 13 | Free | | Platform (account) | | 1 | Free | ### Connect your client The server runs at `https://mcp.rpc.luganodes.com/mcp` over Streamable HTTP and authenticates with your Luganodes API key, sent as a Bearer header. Clients that support remote servers need no local install. **Before you start.** Sign up at [rpc.luganodes.com](https://rpc.luganodes.com/sign-up) and copy the API key from your app page. {% tabs %} {% tab title="Claude code" icon="claude" %} 1. Set your API key in your shell: ```bash export LUGANODES_API_KEY='' ``` 2. Add the server, on one line: {% code overflow="wrap" %} ```bash claude mcp add --scope user --transport http luganodes https://mcp.rpc.luganodes.com/mcp --header "Authorization: Bearer $LUGANODES_API_KEY" ``` {% endcode %} 3. Restart Claude Code, or start a new conversation. 4. Run `/mcp`. You should see `luganodes` connected. {% endtab %} {% tab title="Cursor" icon="cursor" %} 1. Set your API key in your shell: ```bash export LUGANODES_API_KEY='' ``` 2. Add to `~/.cursor/mcp.json` for all projects, or `.cursor/mcp.json` for one project: ```json { "mcpServers": { "luganodes": { "url": "https://mcp.rpc.luganodes.com/mcp", "headers": { "Authorization": "Bearer ${env:LUGANODES_API_KEY}" } } } } ``` 3. Start Cursor from a terminal where `LUGANODES_API_KEY` is set (`open -a Cursor`), or set the variable in your shell profile. 4. Open **Cursor Settings > MCP**. You should see `luganodes` listed. {% endtab %} {% tab title="Claude Desktop" icon="claude" %} 1. Open **Settings > Developer > Edit Config** and add to `claude_desktop_config.json`: ```json { "mcpServers": { "luganodes": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.rpc.luganodes.com/mcp", "--header", "Authorization:${AUTH_HEADER}"], "env": { "AUTH_HEADER": "Bearer " } } } } ``` `mcp-remote` substitutes `AUTH_HEADER` into the header. It needs Node.js. 2. Quit and reopen Claude Desktop. 3. In **Settings > Developer**, `luganodes` should show as running. {% endtab %} {% tab title="VS Code Copilot" icon="vscode" %} 1. Add to `.vscode/mcp.json`: ```json { "servers": { "luganodes": { "type": "http", "url": "https://mcp.rpc.luganodes.com/mcp", "headers": { "Authorization": "Bearer ${input:luganodes-api-key}" } } }, "inputs": [ { "type": "promptString", "id": "luganodes-api-key", "description": "Luganodes API key", "password": true } ] } ``` 2. Click **Start** above `luganodes` in the file, or run **MCP: List Servers**, and enter your API key when prompted. VS Code stores it securely, and the file then shows **Running**. 3. Open Copilot Chat in a **Local** session in **Agent** mode, and ask: "Use the luganodes tool `luga_get_account` to show my plan." Approve the tool call when prompted. {% hint style="info" %} VS Code does not pass servers that use `${input:...}` to Copilot CLI or cloud sessions. Use a Local session. {% endhint %} {% endtab %} {% tab title="Any other client" icon="link-simple" %} Point it at `https://mcp.rpc.luganodes.com/mcp` using Streamable HTTP, and send `Authorization: Bearer ` on every request. Clients that only launch local servers can bridge with `mcp-remote`, as in the Claude Desktop setup. {% endtab %} {% endtabs %} ### Limit what agents can do The MCP server respects your app’s access controls, so you can limit which methods an agent can call, how many compute units it can use each day, and how many requests it can make per second. ### Getting started Once the server is connected, there is nothing to sign in to or select: your API key already ties the server to your app and plan. The typical workflow is: 1. Check the connection, for example "Use `luga_get_account` to show my plan." 2. Ask your agent, for example "What tokens does vitalik.eth hold?" or "Why is my Bitcoin transaction still pending?" ### Bitcoin tools
TOOLDESCRIPTION
btc_get_chain_statusHeight, best block, sync progress, pruning
btc_get_blockTime, transaction count, size, total fees, fee rate percentiles, optional header
btc_get_fee_estimatesFee rate in sat/vB per confirmation target
btc_get_chain_statisticsDifficulty, hash rate in EH/s, transaction throughput
btc_get_mempoolMempool size and minimum fee rate, or one transaction's fee rate, wait time, ancestors and descendants
btc_get_transactionInputs with values, outputs, fee, confirmations
btc_get_utxoWhether an output is unspent, with its value and address
btc_decode_transactionDecoded raw transaction: txid, inputs, outputs, sizes
btc_inspect_psbtPSBT inputs, outputs, fee, next role and what each input is missing
btc_validate_addressValidity and type: P2PKH, P2SH, P2WPKH, P2WSH, P2TR or witness_unknown
btc_verify_messageWhether a signed message matches a legacy (1…) address
btc_verify_transaction_proofWhether a Merkle proof is valid on the active chain, and the txids it proves
### Ethereum Mainnet tools
TOOLDESCRIPTION
eth_get_chain_statusChain ID, latest block, sync state
eth_get_blockTime, miner, gas, base fee, up to 50 transaction hashes
eth_get_gas_pricesGas price, next base fee, priority fee percentiles and blob base fee, in gwei
eth_get_balanceETH balance
eth_get_address_infoContract or account, nonce, EIP-7702 delegate
eth_get_token_balancesBalances of up to 20 ERC-20 tokens in one Multicall3 read
eth_get_token_infoName, symbol, decimals, total supply
eth_get_token_allowanceAmount a spender may move, and whether it is unlimited
eth_get_nft_infoERC-721 or ERC-1155 owner or balance, approval, metadata URI
eth_get_storageOne raw storage slot, with presets for EIP-1967 proxy implementation, admin and beacon
eth_get_transactionFrom, to, value, status, fee, decoded ERC-20 transfers
eth_call_contractDecoded result of a read only contract call
eth_estimate_gasGas a proposed transaction would use
eth_get_block_receiptsEvery receipt in a block: status, gas and log count, first 100 in detail
eth_get_logsUp to 500 logs from up to 5 contracts over at most 1,000 blocks, with Transfer events decoded
eth_simulate_transactionsStatus, gas and return data for up to 10 calls run in sequence
eth_get_txpool_statusPending and queued transaction counts, never contents
eth_trace_transactionInternal call tree, up to 200 frames, with revert reasons
### Ethereum Beacon tools
TOOLDESCRIPTION
beacon_get_chain_statusGenesis, sync status, head slot, justified and finalized epochs
beacon_get_blockHeader with slot, proposer and roots; optional summary of attestations, sync participation, blobs and the execution block
beacon_get_chain_configSpec values, fork schedule or deposit contract
beacon_get_validatorsStatus, balance, effective balance, slashed flag and withdrawal credentials for 1 to 50 validators
beacon_get_validator_dutiesProposer duties for an epoch, or attester and sync duties for up to 100 validators
beacon_get_validator_rewardsBlock proposer reward, or attestation and sync committee rewards for up to 100 validators, in ETH
beacon_get_committeesAttestation committees for a slot, or the sync committee, with membership lists capped
### Tron tools
TOOLDESCRIPTION
tron_get_accountActivation, TRX balance, staked and unstaking TRX, bandwidth and energy
tron_get_blockTime, producer, transaction count, up to 50 transaction IDs
tron_get_transactionStatus, type, from and to, TRX amount, fee, energy and bandwidth, decoded TRC-20 transfers
tron_get_chain_parametersFee and protocol parameters such as the energy fee and unfreeze delay
tron_get_token_balancesBalances of up to 10 TRC-20 tokens
tron_get_token_infoName, symbol, decimals, total supply
tron_get_token_allowanceAmount a spender may move
tron_get_contract_infoDeployer, energy sharing, energy factor and the first 100 function signatures
tron_call_contractDecoded result and energy used, or a revert flag with the revert reason
tron_estimate_energyEnergy a proposed contract call would consume
tron_get_staking_infoTRX staked for bandwidth and energy, pending unstakes, unstake slots left, withdrawable TRX
tron_get_delegated_resourcesAccounts it delegates to and receives from, first 50 each; with a counterparty, amounts and lock expiry
tron_get_logsUp to 500 logs from up to 5 contracts over at most 1,000 blocks, with TRC-20 transfers decoded
### Platform tool
TOOLDESCRIPTION
luga_get_accountPlan, chains the app can use, throughput limit, CU used this cycle and today, and whether access controls are set
### How it works The MCP server is hosted remotely at `https://mcp.rpc.luganodes.com/mcp`, uses Streamable HTTP, and authenticates with your Luganodes API key sent as a Bearer header. When your AI assistant gets a question, it picks the right tool, the server fetches and decodes the data, and the assistant answers in plain language. * **Chain tools** send RPC requests to Luganodes nodes using your app’s key. They follow your app’s access controls and return decoded results. Each tool is charged for the RPC methods it calls, at the rates in the [CU tables](/rpc/compute-units/ethereum-mainnet-cu-table.md), and every result shows the total as `cu_charged`. * **luga\_get\_account** reads your plan, enabled chains and usage directly from your Luganodes account. It costs 0 CU. Before any request reaches a node, the server checks your inputs, your plan and the chains enabled for your app. A tool outside your plan is refused with a message naming the plan it needs. Every tool is read-only. There are no write operations: nothing can sign, send or broadcast a transaction, and simulations and estimates commit nothing to the chain.