abi-to-mcp-guide

UCAI — ABI-to-MCP Server Generator

UCAI (Universal Contract AI Interface) turns any smart contract ABI into a ready-to-use MCP server. One command — any contract on any EVM chain — and your AI agent can interact with it.

The Concept

Smart Contract ABI (JSON)
    │
    ▼
  UCAI CLI
    │
    ▼
MCP Server with tools for every function
    │
    ▼
AI Agent calls contract functions naturally:
  "What's the total supply of this ERC20?"
  "How much can I borrow on Aave?"

Quick Start

Install

pip install abi-to-mcp

Generate MCP Server

# From a verified contract on Etherscan
ucai generate 0xD74f5255D557944cf7Dd0E45FF521520002D5748 --chain arbitrum

# From a local ABI file
ucai generate ./my-contract-abi.json --chain ethereum

# From a well-known protocol
ucai generate uniswap-v3-router --chain ethereum

Use with Claude Desktop

{
  "mcpServers": {
    "my-contract": {
      "command": "ucai",
      "args": ["serve", "0xD74f5255D557944cf7Dd0E45FF521520002D5748", "--chain", "arbitrum"]
    }
  }
}

How It Works

1. ABI Parsing — Reads contract ABI (from Etherscan, local file, or known protocol)
2. Tool Generation — Creates one MCP tool per contract function
3. Type Mapping — Solidity types → JSON Schema types
4. Read/Write Split — Read functions (view/pure) are safe; write functions need signing
5. Documentation — Auto-generates descriptions from function signatures and NatSpec

Generated Tool Example

For a function like:

function balanceOf(address account) external view returns (uint256)

UCAI generates:

{
  "name": "balanceOf",
  "description": "Get the token balance of an account",
  "parameters": {
    "account": { "type": "string", "description": "The account address (address)" }
  }
}

Supported Chains