Foundry Zksync
Let your coding agent run forge, cast, and anvil-zksync from chat while you compile, deploy, and debug zkSync Era contracts.
Overview
io.github.Jrigada/foundry-zksync is a MCP server for the Build phase that exposes forge, cast, and anvil-zksync for zkSync Era smart-contract development from your agent.
What is this MCP server?
- Stdio MCP wrapping foundry-zksync forge, cast, and anvil-zksync
- npm package foundry-zksync-mcp v0.2.3 for agent-driven zkSync Era workflows
- Supports compile, test, deploy, and cast read/write patterns without leaving the IDE
- Targets zkSync Era specifically—not generic Ethereum mainnet Foundry
- Server schema version 0.2.3
- Stdio transport via npm identifier foundry-zksync-mcp
- Three tool families: forge, cast, anvil-zksync per server description
What problem does it solve?
Agents cannot run zkSync-specific Foundry commands unless you paste terminal output or manually bridge every compile and cast step.
Who is it for?
Indie builders and small teams targeting zkSync Era who already use foundry-zksync and want agent-assisted compile, test, and cast workflows.
Skip if: Teams on vanilla Ethereum-only Foundry without zkSync, or builders who only need a one-off script with no ongoing agent integration.
What do I get? / Deliverables
After you register the stdio server, your agent can invoke foundry-zksync operations directly while you stay in one chat thread for contract iteration.
- Agent-callable forge build and test runs for zkSync projects
- cast-style RPC queries and writes mediated through MCP
- Local anvil-zksync sessions driven from the agent
Recommended MCP Servers
Journey fit
How it compares
MCP bridge to foundry-zksync CLIs, not a hosted zkSync RPC or managed deployment platform.
Common Questions / FAQ
Who is io.github.Jrigada/foundry-zksync for?
Solo builders and developers shipping on zkSync Era who want their AI coding agent to run forge, cast, and anvil-zksync without manual terminal handoffs.
When should I use io.github.Jrigada/foundry-zksync?
Use it during active contract build and test cycles when you are iterating Solidity or zkSync tooling and want MCP tool calls instead of copy-paste logs.
How do I add io.github.Jrigada/foundry-zksync to my agent?
Install the npm package foundry-zksync-mcp, ensure foundry-zksync is on your PATH, and add a stdio MCP entry pointing at that package in Claude Code, Cursor, or your client’s MCP config.