Mcp Contracts
Pull smart contract ABIs and on-chain contract data for EVM and Solana into agent-assisted integration and debugging work.
Overview
io.github.CryptoAPIs-io/mcp-contracts is a Build-phase MCP server that serves smart contract ABIs and on-chain contract data for EVM and Solana via Crypto APIs.
What is this MCP server?
- Exposes smart contract ABIs and on-chain data for EVM and Solana through Crypto APIs
- Stdio MCP @cryptoapis-io/mcp-contracts at version 0.3.0
- Single required credential: CRYPTOAPIS_API_KEY
- Complements mcp-broadcast and mcp-hd-wallet for read-then-act Web3 workflows
- Agent-facing contract lookup—not a Solidity compiler or deployment pipeline
- Server version 0.3.0 per MCP server schema
- Supports EVM and Solana per package description
- 1 required env var: CRYPTOAPIS_API_KEY
What problem does it solve?
Implementing against live protocols means constantly hunting ABIs and chain reads across explorers instead of one agent-accessible source.
Who is it for?
Builders coding EVM or Solana integrations who want ABI and contract state available inside Claude Code, Cursor, or Codex sessions.
Skip if: Teams that only need static ABIs committed in-repo with no live chain queries, or non-Crypto APIs data sources.
What do I get? / Deliverables
Your agent can query contract ABIs and on-chain data through Crypto APIs while you build integrations with fewer context switches.
- Agent-accessible ABI and contract data queries for supported chains
- Faster integration scaffolding against live protocols
- Stdio MCP server registered alongside other Crypto APIs MCPs
Recommended MCP Servers
Journey fit
Contract metadata and reads land while you implement calls, indexers, or agent tools—not during initial idea research alone. It is a direct Crypto APIs bridge for ABIs and chain state your build needs when coding against live contracts.
How it compares
Read-focused contract MCP over Crypto APIs, not a deployment or audit skill.
Common Questions / FAQ
Who is mcp-contracts for?
Developers and solo founders building on EVM or Solana who want agents to pull ABIs and contract data from Crypto APIs during implementation.
When should I use mcp-contracts?
Use it in Build when you are wiring contract calls, decoding events, or verifying on-chain state against known addresses.
How do I add mcp-contracts to my agent?
Add @cryptoapis-io/mcp-contracts as a stdio MCP server, export CRYPTOAPIS_API_KEY, and reference the server definition from the CryptoAPIs-io GitHub repository in your agent MCP settings.