Integration

Infura integration

Infura provides scalable Ethereum and Web3 infrastructure via JSON-RPC APIs. Access real-time blockchain data, send transactions, query smart contracts, and build decentralized applications. Supports Ethereum mainnet, testnets (Sepolia, Holesky), and multiple EVM-compatible networks. Trusted by millions of developers and powering major Web3 applications including MetaMask.

Connect Infura How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Infura.Built from the 22 Infura tools below, on the connection you add once.

Common Infura use cases

block explorer
fee estimation
state verification
network verification
event indexing
wallet connection
contract debugging
network monitoring
infrastructure monitoring
sending ETH

What you can do with Infura

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Block, 4 operations

get_block_by_hashGet block by hashPOSTGets block information by its hash. Params: block hash (32-byte hex), boolean for full transactions. Returns block header, hash, transactions, and metadata.
get_block_by_numberGet block by numberPOSTGets block information by number. Params: block number (hex or tag like 'latest', 'pending', 'earliest', 'safe', 'finalized'), boolean for full transactions. Returns block header, hash, transactions, and metadata.
get_block_numberGet block numberPOSTGets the current block number of the Ethereum network. Returns hex-encoded block height. Essential for tracking confirmations, sync status, and determining the latest chain state.
get_block_receiptsGet block receiptsPOSTGets all transaction receipts for a block. Param: block number (hex) or tag. Returns array of receipt objects with status, gasUsed, logs for every transaction.

Network, 4 operations

get_chain_idGet chain idPOSTGets the EIP-155 chain ID as hex. Returns '0x1' for mainnet, '0xaa36a7' for Sepolia. Used in transaction signing to prevent cross-chain replay attacks.
get_client_versionGet client versionPOSTGets the Ethereum client version. Returns a string like 'Geth/v1.11.6-omnibus-f83e1598/linux-amd64/go1.20.3' identifying the node implementation.
get_network_versionGet network versionPOSTGets the current network ID as a string. Returns '1' for Ethereum mainnet, '11155111' for Sepolia, etc. Use to verify you're connected to the expected network.
get_syncing_statusGet syncing statusPOSTChecks the sync status of the node. Returns false when fully synced, or an object with startingBlock, currentBlock, highestBlock when syncing.

Transaction, 4 operations

get_transaction_by_hashGet transaction by hashPOSTGets transaction details by hash. Returns from, to, value, gas, gasPrice, input, nonce, blockNumber, blockHash, transactionIndex. Null if pending or not found.
get_transaction_countGet transaction countPOSTGets the number of transactions sent from an address (nonce). Params: address, block tag. Returns hex count. Use 'pending' tag to include mempool transactions for correct next nonce.
get_transaction_receiptGet transaction receiptPOSTGets the receipt of a mined transaction. Returns status (1=success, 0=reverted), gasUsed, logs (events), blockNumber, and contractAddress (if deployment). Null if not yet mined.
send_raw_transactionSend raw transactionPOSTBroadcasts a signed transaction to the network. Param is the hex-encoded signed transaction data. Returns transaction hash (32 bytes). Transaction must be pre-signed with private key client-side.

Gas, 3 operations

estimate_gasEstimate gasPOSTEstimates gas required to execute a transaction. Simulates the call and returns expected gas consumption (hex). Use to set gas limit before sending transactions.
get_gas_priceGet gas pricePOSTGets the current gas price in wei (hex). Returns the node's estimate of a reasonable gas price based on recent blocks. Multiply by gas units for total transaction cost.
get_max_priority_feeGet max priority feePOSTGets the recommended priority fee (tip) for EIP-1559 transactions. Returns hex amount in wei needed for block inclusion. No parameters required.

Contract, 2 operations

call_contractCall contractPOSTExecutes a contract function locally without creating a transaction. Read contract state (balances, allowances, etc.) for free. Params: call object (from optional, to, data, optional gas/value), block tag.
get_codeGet codePOSTGets the bytecode deployed at an address. Params: address, block tag. Returns '0x' for EOA (externally owned account) or contract bytecode if contract exists.

Account, 1 operation

get_proofGet proofPOSTGets Merkle proof for an account and storage keys. Params: address, array of storage keys, block tag. Returns balance, codeHash, nonce, storageHash, accountProof, storageProof.

Balance, 1 operation

get_balanceGet balancePOSTGets the native ETH balance of an address in wei. Params: address (0x-prefixed), block tag ('latest', 'pending', 'earliest', 'safe', 'finalized', or hex block number). Divide result by 10^18 for ETH.

Fee, 1 operation

get_fee_historyGet fee historyPOSTGets historical fee data for EIP-1559 gas estimation. Params: block count (1-1024), newest block, optional percentile array. Returns baseFeePerGas, gasUsedRatio, and reward per percentile.

Log, 1 operation

get_logsGet logsPOSTGets event logs matching filter criteria. Filter by block range, contract address(es), and indexed topics. Essential for tracking token transfers, DEX swaps, and contract events.

Storage, 1 operation

get_storage_atGet storage atPOSTGets the value at a specific storage slot of a contract. Params: address, storage position (hex slot index), block tag. Returns 32-byte hex value at that slot.

Use Infura from Claude Code, Cursor or Codex

Connect Infura in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Infura operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Infura

Create your workspace
Sign up free. Nothing to install.
Connect Infura once
Add your Infura connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Infura integration FAQ

What can you do with the Infura integration?

LiveContext exposes 22 operations on Infura, covering block, network, transaction and gas. Common uses include block explorer, fee estimation and state verification.