Universal Blockchain
Expose ZetaChain universal-chain operations to your coding agent through MCP instead of maintaining separate cross-chain scripts.
Overview
Universal Blockchain is a Build-phase MCP server that connects AI agents to ZetaChain universal blockchain operations.
What is this MCP server?
- ZetaChain-focused universal blockchain MCP server
- stdio npm package universal-blockchain-mcp (v1.0.2)
- GitHub source at ExpertVagabond/universal-blockchain-mcp
- Agent-oriented bridge for omnichain / universal chain tasks on ZetaChain
- Fits standard MCP stdio registration in Claude Code and Cursor
- Server version 1.0.2
- npm identifier universal-blockchain-mcp
- stdio transport
What problem does it solve?
ZetaChain workflows are hard to drive from an agent when you only have ad-hoc SDK scripts and no MCP tool surface.
Who is it for?
Solo builders targeting ZetaChain omnichain apps who want MCP-native chain tooling beside their codebase.
Skip if: Teams not using ZetaChain or builders who need a multi-chain aggregator with documented tool counts in the registry blurb.
What do I get? / Deliverables
After registration, your agent can invoke ZetaChain-oriented MCP tools for universal-chain tasks from your IDE host.
- Registered ZetaChain universal blockchain MCP server
- Agent-callable chain tooling via stdio transport
- Consolidated cross-chain integration surface for build workflows
Recommended MCP Servers
Journey fit
How it compares
ZetaChain-specific chain MCP, not a general-purpose EVM wallet skill or marketplace plugin bundle.
Common Questions / FAQ
Who is universal-blockchain for?
Indie developers building on ZetaChain who use MCP-enabled agents and want universal-chain actions exposed as tools.
When should I use universal-blockchain?
Use it while integrating ZetaChain reads, transfers, or universal-app flows during the build phase of your agent-assisted project.
How do I add universal-blockchain to my agent?
Install universal-blockchain-mcp from npm, add a stdio MCP server entry in Claude Code or Cursor, and configure any keys or endpoints required by the GitHub project.