Ucai MCP Server

<strong>🙇‍♀️ Universal Contract AI Interface</strong> <strong>☑️ UCAI in Anthropic MCP Registry</strong> &nbsp;&nbsp;|&nbsp;&nbsp; <strong>🌐 Try

Remote serverstreamable-httpPython

What is the Ucai MCP server?

If you already use Ucai, the ucai mcp server is the piece that lets your assistant work with it directly. 🙇‍♀️ Universal Contract AI Interface ☑️ UCAI in Anthropic MCP Registry   |   🌐 Try the Web Builder →   |   📖 Documentation.

What the server does

Found a contract on Etherscan? One command. Claude can now use it.

  • Writing MCP server boilerplate is tedious
  • Mapping Solidity types to JSON Schema is error-prone
  • Every contract needs the same patterns repeated
  • Safety (simulation, gas limits) is easy to forget

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Vibecoders — Ship faster with AI-generated blockchain tools
  • Pre — configured claude_config.json
  • source — ABI file path or contract address
  • CRITICAL — The CRITICAL tool exposed by this server
  • HIGH — The HIGH tool exposed by this server
  • POSITIVES — The POSITIVES tool exposed by this server
  • Severity — Examples
  • Template — Contracts
  • address — string with pattern
  • uint256 — string (for precision)
  • uint8-uint32 — integer with bounds
  • bool — boolean

Credentials and setup notes

Configuration is passed through the environment: RPC_URL, PRIVATE_KEY, ETHERSCAN_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ucai.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ucai's toolset — Vibecoders, Pre, source and 11 more — is a fair guide to whether it matches your workflow. It is maintained by nirholas; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
VibecodersShip faster with AI-generated blockchain tools
Preconfigured claude_config.json
sourceABI file path or contract address
CRITICALThe CRITICAL tool exposed by this server.
HIGHThe HIGH tool exposed by this server.
POSITIVESThe POSITIVES tool exposed by this server.
SeverityExamples
TemplateContracts
addressstring with pattern
uint256string (for precision)
uint8-uint32integer with bounds
boolboolean
stringstring
bytesstring with pattern

How to install the Ucai MCP server

{
  "mcpServers": {
    "ucai": {
      "command": "uvx",
      "args": ["abi-to-mcp"],
      "env": {
        "RPC_URL": "your-value",
        "PRIVATE_KEY": "your-value",
        "ETHERSCAN_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
RPC_URLEndpoint or connection string the server talks to.Yes
PRIVATE_KEYCredential the server authenticates with.Yes
ETHERSCAN_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Ucai to Vibecoders.
  • Use Ucai to Pre.
  • Use Ucai to source.

Frequently asked questions

It connects Ucai to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Vibecoders, Pre, source, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ucai directly.