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
- Clone the repository:
git clone https://github.com/celo-org/celo-mcp
cd celo-mcp
- Install dependencies:
pip install -e .
- Set up environment variables (optional):
export CELO_RPC_URL="https://forno.celo.org" # Default: Celo mainnet
export CELO_TESTNET_RPC_URL="https://alfajores-forno.celo-testnet.org" # Alfajores testnet
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):
{
"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):
{
"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:
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:
{
"mcpServers": {
"celo": { "url": "https://<your-host>/mcp" }
}
}
Configuration (environment variables):
| Var | Purpose | Default |
|---|---|---|
MCP_TRANSPORT |
stdio or http |
stdio |
HOST / PORT |
HTTP bind host / port | 127.0.0.1 / 3000 |
MCP_ALLOWED_HOSTS |
Hostnames accepted by the SDK's DNS-rebinding check, comma-separated. Set to your public hostname(s), or * to disable the check |
localhost only |
MCP_CORS_ORIGINS |
Comma-separated allowed origins (or *) |
* |
MCP_RATE_LIMIT / MCP_RATE_WINDOW |
Requests per client per window (seconds); /health is exempt |
60 / 60 |
MCP_TRUST_PROXY |
Number 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 deployment |
unset |
MCP_AUTH_TOKEN |
If set, requires Authorization: Bearer <token> on /mcp |
unset (open) |
CELO_RPC_URL |
Celo RPC endpoint | (existing default) |
GET /health returns 200 for hosting health checks. See
docs/DEPLOYMENT.md for container/hosting instructions.
Usage
Running the Server
# Run the MCP server
python -m celo_mcp.server
# Or use the CLI entry point
celo-mcp-server
Available Tools
Blockchain Data Operations
-
get_network_status
- Get current network status and connection information
- No parameters required
-
get_block
- Fetch block information by number, hash, or "latest"
- Parameters:
block_identifier,include_transactions(optional)
-
get_transaction
- Get transaction details by hash
- Parameters:
tx_hash
-
get_account
- Get account information including balance and nonce
- Parameters:
address
-
get_latest_blocks
- Get information about recent blocks
- Parameters:
count(optional, default: 10, max: 100)
Token Operations
-
get_token_info
- Get detailed token information (name, symbol, decimals, supply)
- Parameters:
token_address
-
get_token_balance
- Get token balance for a specific address
- Parameters:
token_address,address
-
get_celo_balances
- Get CELO and stable token balances for an address
- Parameters:
address
NFT Operations
-
get_nft_info
- Get NFT information including metadata and collection details
- Parameters:
contract_address,token_id
-
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
-
call_contract_function
- Call a read-only contract function
- Parameters:
contract_address,function_name,abi,function_args(optional),from_address(optional)
-
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
-
estimate_transaction
- Estimate gas and cost for a transaction
- Parameters:
to,from_address,value(optional),data(optional)
-
get_gas_fee_data
- Get current gas fee data including EIP-1559 fees
- No parameters required
Governance Operations
-
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)
-
get_proposal_details
- Get detailed information about a specific governance proposal including content and voting history
- Parameters:
proposal_id
Staking Operations
-
get_staking_balances
- Get staking balances for an address, including active and pending stakes broken down by validator group
- Parameters:
address
-
get_activatable_stakes
- Get information about pending stakes that can be activated for earning rewards
- Parameters:
address
-
get_validator_groups
- Get information about all validator groups, including their members, votes, capacity, and performance metrics
- No parameters required
-
get_validator_group_details
- Get detailed information about a specific validator group including its members and performance data
- Parameters:
group_address
-
get_total_staking_info
- Get network-wide staking information including total votes and participation metrics
- No parameters required
Key Features
Token Support
- ERC20 Standard: Full support for ERC20 tokens
- Celo Stable Tokens: Built-in support for cUSD, cEUR, and cREAL
- 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
# Install development dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run with coverage
pytest --cov=celo_mcp
Code Quality
# Format code
black src/
isort src/
# Lint code
flake8 src/
mypy src/
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests for new functionality
- Ensure all tests pass
- 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:
- Check the existing issues on GitHub
- Create a new issue with detailed information
- 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
Metadata
Release files for celo-mcp 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| celo_mcp-0.4.1.tar.gz | 203.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| celo_mcp-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 282.1 kB
Release files / celo_mcp-0.4.1.tar.gz
| Download URL | celo_mcp-0.4.1.tar.gz |
|---|---|
| Size | 203.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c700f7dd8d89c9312888b104677a8f85a30051808dd83f80b3cd0e750280868
|
|
BLAKE2b-256 checksum How to use checksums |
cce992ff7c44664001f79e9ac311418e8f2610717a0e303ff83113a69d5ec854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / celo_mcp-0.4.1-py3-none-any.whl
| Download URL | celo_mcp-0.4.1-py3-none-any.whl |
|---|---|
| Size | 78.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1d1ed2d556caa13b673514743bd1d1de9ab56cf3276ab763cd1733c725b118f
|
|
BLAKE2b-256 checksum How to use checksums |
67bf6584912c8d5f794f7bac5afbac9ae4342939a9c169ea65b5d24e659c8e48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency log