Celo MCP Server

org.celoPublished by celo.orgv0.4.3Updated Oct 30, 2026

Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking

The publisher's own server: Celo Docs

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Read-only MCP server for the Celo blockchain: lets an assistant look up blocks, transactions, token balances, governance proposals, staking data and request…

What you can do
  • Inspect network status, blocks, latest blocks and transactions by hash or number
  • Check CELO, stable token and ERC20 balances, plus gas fee data
  • Read governance proposals and proposal details with voting history
  • Review staking balances, activatable stakes, validator groups and network-wide staking metrics
  • Request testnet CELO from the Celo faucet and poll the payout status
When to use it
Useful when you want an assistant to answer questions about Celo on-chain activity, wallet balances, governance or validator staking, or to fetch testnet CELO for development on Celo Sepolia.
Requirements
Runs locally as a Python package via uvx or pip. Optional environment variables: CELO_MCP_RPC_URL (defaults to Forno), CELO_MCP_USE_TESTNET, and CELO_MCP_FAUCET_API_KEY to enable the faucet tools. Network access to a Celo RPC endpoint is required. An optional HTTP transport exists with its own host, CORS, rate-limit and MCP_AUTH_TOKEN settings.
Before you install
The faucet tools spend a limited allowance tied to CELO_MCP_FAUCET_API_KEY (10 requests per 24 hours per account and address); only use the key with stdio or authenticated deployments, since an open HTTP endpoint lets anyone spend it and the key can be revoked. Faucet requests send testnet CELO to an address you specify. The README lists extra tools (NFT, contract calls, account info) that are not in the published tool set.

Installation

In SourceWeft

  1. Open Celo MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Celo MCP Server

A Model Context Protocol (MCP) server for interacting with the Celo blockchain. This server provides comprehensive access to Celo blockchain data, token operations, NFT management, smart contract interactions, transaction handling, and governance operations.

Installation

  1. Clone the repository:
bash
git clone https://github.com/celo-org/celo-mcpcd celo-mcp
  1. Install dependencies:
bash
pip install -e .
  1. Set up environment variables (optional):
bash
export CELO_MCP_RPC_URL="https://forno.celo.org"  # Default: Celo mainnetexport CELO_MCP_USE_TESTNET=true                  # Use Celo Sepolia instead

MCP Integration

Cursor IDE Integration

To use this MCP server with Cursor IDE, add the following configuration to your MCP settings file (~/.cursor/mcp.json):

json
{  "mcpServers": {    "celo-mcp": {      "command": "uvx",      "args": ["--refresh", "celo-mcp"]    }  }}

The --refresh flag ensures that the latest code is always loaded when the MCP server starts.

Claude Desktop Integration

For Claude Desktop, add this configuration to your MCP settings file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{  "mcpServers": {    "celo-mcp": {      "command": "uvx",      "args": ["--refresh", "celo-mcp"]    }  }}

Connect remotely (Streamable HTTP)

The server can also run as a remote MCP endpoint over Streamable HTTP, so clients connect with a single URL — no local Python install. The stdio setup above is unchanged; this is an additional transport.

Run it in HTTP mode:

bash
celo-mcp-server --transport http --port 3000# or via env:MCP_TRANSPORT=http PORT=3000 celo-mcp-server

Then point any remote-capable MCP client at the URL:

json
{  "mcpServers": {    "celo": { "url": "https://<your-host>/mcp" }  }}

Configuration (environment variables):

VarPurposeDefault
MCP_TRANSPORTstdio or httpstdio
HOST / PORTHTTP bind host / port127.0.0.1 / 3000
MCP_ALLOWED_HOSTSHostnames accepted by the SDK's DNS-rebinding check, comma-separated. Set to your public hostname(s), or * to disable the checklocalhost only
MCP_CORS_ORIGINSComma-separated allowed origins (or *)*
MCP_RATE_LIMIT / MCP_RATE_WINDOWRequests per client per window (seconds); /health is exempt60 / 60
MCP_TRUST_PROXYNumber of X-Forwarded-For hops your infrastructure appends, so the rate limiter keys on the client rather than the proxy address. 1 for a single reverse proxy, 2 behind a Google external load balancer. Counted from the right — see deploymentunset
MCP_AUTH_TOKENIf set, requires Authorization: Bearer <token> on /mcpunset (open)
CELO_MCP_RPC_URLCelo RPC endpointForno for the selected network
CELO_MCP_USE_TESTNETUse Celo Sepolia (chain ID 11142220) instead of mainnetfalse
CELO_MCP_FAUCET_API_KEYEnables the faucet tools. Create one at faucet.celo.org/keys — see Faucet accessunset (faucet tools disabled)

GET /health returns 200 for hosting health checks. See docs/DEPLOYMENT.md for container/hosting instructions.

Usage

Running the Server

bash
# Run the MCP serverpython -m celo_mcp.server
# Or use the CLI entry pointcelo-mcp-server

Available Tools

Blockchain Data Operations
  1. get_network_status

    • Get current network status and connection information
    • No parameters required
  2. get_block

    • Fetch block information by number, hash, or "latest"
    • Parameters: block_identifier, include_transactions (optional)
  3. get_transaction

    • Get transaction details by hash
    • Parameters: tx_hash
  4. get_account

    • Get account information including balance and nonce
    • Parameters: address
  5. get_latest_blocks

    • Get information about recent blocks
    • Parameters: count (optional, default: 10, max: 100)
Token Operations
  1. get_token_info

    • Get detailed token information (name, symbol, decimals, supply)
    • Parameters: token_address
  2. get_token_balance

    • Get token balance for a specific address
    • Parameters: token_address, address
  3. get_celo_balances

    • Get CELO and stable token balances for an address
    • Parameters: address
NFT Operations
  1. get_nft_info

    • Get NFT information including metadata and collection details
    • Parameters: contract_address, token_id
  2. get_nft_balance

    • Get NFT balance for an address (supports ERC721 and ERC1155)
    • Parameters: contract_address, address, token_id (optional for ERC1155)
Smart Contract Operations
  1. call_contract_function

    • Call a read-only contract function
    • Parameters: contract_address, function_name, abi, function_args (optional), from_address (optional)
  2. estimate_contract_gas

    • Estimate gas for a contract function call
    • Parameters: contract_address, function_name, abi, from_address, function_args (optional), value (optional)
Transaction Operations
  1. estimate_transaction

    • Estimate gas and cost for a transaction
    • Parameters: to, from_address, value (optional), data (optional)
  2. get_gas_fee_data

    • Get current gas fee data including EIP-1559 fees
    • No parameters required
Governance Operations
  1. get_governance_proposals

    • Get Celo governance proposals with pagination support
    • Parameters: include_inactive (optional), include_metadata (optional), page (optional), page_size (optional), offset (optional), limit (optional)
  2. get_proposal_details

    • Get detailed information about a specific governance proposal including content and voting history
    • Parameters: proposal_id
Staking Operations
  1. get_staking_balances

    • Get staking balances for an address, including active and pending stakes broken down by validator group
    • Parameters: address
  2. get_activatable_stakes

    • Get information about pending stakes that can be activated for earning rewards
    • Parameters: address
  3. get_validator_groups

    • Get information about all validator groups, including their members, votes, capacity, and performance metrics
    • No parameters required
  4. get_validator_group_details

    • Get detailed information about a specific validator group including its members and performance data
    • Parameters: group_address
  5. get_total_staking_info

    • Get network-wide staking information including total votes and participation metrics
    • No parameters required
Faucet Operations

Both faucet tools are testnet-only and require CELO_MCP_FAUCET_API_KEY (see Faucet access below).

  1. request_faucet_funds

    • Request testnet CELO for an address. Returns the payout transaction hash if it lands while the request is open, otherwise a request_key to poll with
    • Sends 3 CELO per request, and CELO only — no USDm or other stablecoins
    • Parameters: beneficiary, optional network (celo-sepolia), optional wait (default true)
  2. get_faucet_request_status

    • Check whether a queued faucet request has paid out
    • Parameters: request_key, optional network (celo-sepolia)

Faucet access

The faucet's browser flow is gated on reCAPTCHA v3, which scores headless callers badly, so the faucet tools use its API-key path instead. Create a key at faucet.celo.org/keys (sign in with GitHub; up to 2 keys, 90-day expiry) and set it in your MCP client's env block:

json
{  "mcpServers": {    "celo-mcp": {      "command": "uvx",      "args": ["celo-mcp"],      "env": { "CELO_MCP_FAUCET_API_KEY": "cfk_..." }    }  }}

The key is read from the environment and never passed as a tool argument, so it does not enter the model's context or the conversation transcript.

Limits are set by the faucet, not by this server: 10 requests per 24 hours, counted per GitHub account and per beneficiary address — holding two keys does not double the allowance. Global daily and 10-minute burst ceilings apply across all keys on top of that. celo-sepolia (chain ID 11142220) is the only supported network; there is no mainnet faucet.

The faucet publishes its API contract at openapi.json and llms-full.txt; treat those as the source of truth if amounts or limits change.

Deployment note: the HTTP transport is open unless MCP_AUTH_TOKEN is set. Only configure a faucet key for stdio or authenticated deployments — otherwise anyone reaching /mcp can spend your daily allowance on arbitrary addresses, and the key can be revoked for abuse.

Key Features

Token Support

  • ERC20 Standard: Full support for ERC20 tokens
  • Mento Stable Tokens: Built-in support for USDm, EURm and BRLm (formerly cUSD, cEUR and cREAL), plus XOFm, KESm, PHPm, COPm and GHSm
  • Balance Queries: Get token balances with proper decimal formatting
  • Token Information: Retrieve name, symbol, decimals, and total supply

NFT Support

  • Multi-Standard: Support for both ERC721 and ERC1155 standards
  • Automatic Detection: Automatically detects NFT standard using ERC165
  • Metadata Fetching: Retrieves and parses NFT metadata from URIs
  • IPFS Support: Built-in IPFS gateway support for metadata
  • Collection Information: Get collection-level information

Smart Contract Interactions

  • Function Calls: Call read-only contract functions
  • Gas Estimation: Estimate gas costs for contract interactions
  • ABI Management: Parse and manage contract ABIs
  • Event Handling: Retrieve and decode contract events
  • Transaction Building: Build contract transactions

Transaction Management

  • Gas Estimation: Accurate gas estimation for transactions
  • EIP-1559 Support: Modern fee structure with base fee and priority fee
  • Transaction Simulation: Simulate transactions before execution
  • Fee Calculation: Dynamic fee calculation based on network conditions

Governance Support

  • Proposal Management: Retrieve and analyze Celo governance proposals
  • Voting Data: Access proposal voting history and results
  • Metadata Integration: Fetch proposal metadata from GitHub repositories
  • Pagination Support: Efficiently browse through large sets of proposals

Staking Support

  • Staking Balances: View active and pending stakes by validator group
  • Activation Tracking: Check which pending stakes can be activated
  • Validator Information: Comprehensive validator and validator group data
  • Performance Metrics: Validator scores, election status, and capacity
  • Network Statistics: Total voting power and staking participation

Development

Running Tests

bash
# Install development dependenciespip install -e ".[dev]"
# Run testspytest
# Run with coveragepytest --cov=celo_mcp

Code Quality

bash
# Format codeblack src/isort src/
# Lint codeflake8 src/mypy src/

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests for new functionality
  5. Ensure all tests pass
  6. Submit a pull request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

For questions, issues, or contributions, please:

  1. Check the existing issues on GitHub
  2. Create a new issue with detailed information
  3. Join the community discussions

Acknowledgments

  • Built on the Model Context Protocol (MCP) framework
  • Uses Web3.py for Ethereum/Celo blockchain interactions
  • Supports the Celo ecosystem and its stable token infrastructure

Source: README.md at commit f2c1bac

Tools

17

get_network_status

Retrieve the current status and connection information of the Celo network, including network health and connectivity details.

Takes no parameters.

get_block

Fetch detailed information about a specific block on the Celo blockchain using its number or hash. Optionally include full transaction details within the block.

Parametersblock_identifierrequiredinclude_transactions

get_transaction

Obtain detailed information about a specific transaction on the Celo blockchain using its transaction hash.

Parameterstx_hashrequired

get_latest_blocks

Get information about the most recent blocks on the Celo blockchain, with the ability to specify the number of blocks to retrieve and starting offset.

Parameterscountoffset

get_token_balance

Get the token balance for a specific address.

Parametersaddressrequiredtoken_addressrequired

get_celo_balances

Get CELO and stable token balances for an address.

Parametersaddressrequired

get_stable_token_balance

Get balances of all major stable tokens and CELO for an address using multicall.

Parametersaddressrequired

get_gas_fee_data

Get current gas fee data including EIP-1559 fees.

Takes no parameters.

get_governance_proposals

Get Celo governance proposals with pagination support.

Parameterspagelimitoffsetpage_sizeinclude_inactiveinclude_metadata

get_proposal_details

Get detailed information about a specific governance proposal including its content and voting history.

Parametersproposal_idrequired

get_staking_balances

Get staking balances for an address, including active and pending stakes broken down by validator group.

Parametersaddressrequired

get_activatable_stakes

Get information about pending stakes that can be activated for earning rewards.

Parametersaddressrequired

get_validator_groups

Get information about all validator groups, including their members, votes, capacity, and performance metrics.

Parameterspagelimitoffsetpage_size

get_validator_group_details

Get detailed information about a specific validator group including its members and performance data.

Parametersgroup_addressrequired

get_total_staking_info

Get network-wide staking information including total votes and participation metrics.

Takes no parameters.

request_faucet_funds

Request testnet CELO from the Celo faucet for an address. Testnet only (celo-sepolia); there is no mainnet faucet. Sends 3 CELO per request; dispenses CELO only - no USDm or other stablecoins. Requires the CELO_MCP_FAUCET_API_KEY environment variable, set to a key created at https://faucet.celo.org/keys. Limited to 10 requests per 24 hours, per account and per beneficiary address. Returns the payout transaction hash if it lands while the request is open, otherwise a request_key to check with get_faucet_request_status.

Parameterswaitnetworkbeneficiaryrequired

get_faucet_request_status

Check whether a queued faucet request has paid out, using the request_key returned by request_faucet_funds. Returns the payout transaction hash once the status is Done.

Parametersnetworkrequest_keyrequired

Version history

1
  1. v0.4.3LatestOct 30, 2026

Score

80% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Celo integrations