Ava Genesis
Deploy an ERC-20 token on Ethereum, Base, BNB Chain, or Polygon from your AI coding agent without hand-rolling deploy scripts or separate dashboards.
Overview
Ava Genesis (io.github.avagenesisdev/ava-genesis) is an MCP server for the Build phase that deploys ERC-20 tokens on Ethereum, Base, BNB Chain, and Polygon in one authenticated remote call.
What is this MCP server?
- One MCP call deploys a live ERC-20 contract instead of a multi-step CLI or manual remix flow
- Supports four networks: Ethereum, Base, BNB Chain (BNB), and Polygon
- Remote streamable-http endpoint at https://avagenesis.com/api/mcp (MCP schema 2025-12-11)
- Authenticated with an Ava Genesis API key (ava_live_...) created in the Ava dashboard
- Server version 2.0.0 with contract deployment as the primary capability
- 4 EVM networks supported: Ethereum, Base, BNB Chain, Polygon
- MCP server schema version 2025-12-11
- Published server version 2.0.0
What problem does it solve?
Deploying the same ERC-20 idea across multiple EVM networks usually means different scripts, keys, and checklists that pull you out of your agent workflow.
Who is it for?
Indie builders and small teams who already use MCP in Claude Code or Cursor and want a fast, repeatable ERC-20 launch on Ethereum, Base, BNB Chain, or Polygon.
Skip if: Teams that need bespoke smart-contract logic, non-EVM chains, or fully local/offline deployment with no third-party API.
What do I get? / Deliverables
After you add the remote MCP and API key, your agent can return a deployed ERC-20 contract on your chosen supported chain without a separate deploy session.
- Deployed ERC-20 smart contract on a selected supported chain (Ethereum, Base, BNB Chain, or Polygon)
- Contract address and deployment outcome usable in your app or docs
- Repeatable agent-driven deploy path for additional networks via the same MCP config
Recommended MCP Servers
Journey fit
Token contract deployment is core product work once you are past idea validation—solo builders wire on-chain assets into apps and experiments during the build phase. Ava Genesis is exposed as a remote MCP (streamable HTTP), so it belongs on the integrations shelf: your agent calls one tool instead of maintaining chain-specific deploy tooling.
How it compares
Remote MCP token-deployment API, not an in-repo agent skill or a general-purpose Solidity codegen workflow.
Common Questions / FAQ
Who is Ava Genesis for?
Solo builders and developers who ship with MCP-enabled agents and want to deploy standard ERC-20 tokens on major EVM networks without maintaining per-chain deploy scripts.
When should I use Ava Genesis?
Use it during build when you have token parameters decided and need a deployed contract on Ethereum, Base, BNB Chain, or Polygon from inside your agent session.
How do I add Ava Genesis to my agent?
Register the remote MCP URL https://avagenesis.com/api/mcp (streamable HTTP), set the AVA_API_KEY secret to your ava_live_ key from https://avagenesis.com/api/agents/keys, then invoke the server’s deploy tools from your MCP client.