Expose foundry-zksync (forge, cast, anvil-zksync) tools for zkSync Era development
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Foundry Zksync.
initforge init` with automatic zkSync config
compileforge build --zksync
testforge test --zksync` with filter/verbosity options
run_scriptforge script --zksync` with broadcast, sender, slow mode
deployforge create --zksync` with structured output parsing
verifyforge verify-contract --zksync` (Etherscan & zkSync Explorer)
An MCP (Model Context Protocol) server that exposes foundry-zksync CLI tools to AI assistants like Claude.
| Tool | Description |
|---|---|
init | forge init with automatic zkSync config |
compile | forge build --zksync |
test | forge test --zksync with filter/verbosity options |
run_script | forge script --zksync with broadcast, sender, slow mode |
deploy | forge create --zksync with structured output parsing |
verify | forge verify-contract --zksync (Etherscan & zkSync Explorer) |
install | forge install for dependency management |
clean | forge clean to remove build artifacts |
gas_report | forge test --gas-report for gas usage analysis |
snapshot | forge snapshot for gas benchmarking |
read_foundry_toml | Read and inspect project configuration |
explain | Match errors/logs against a knowledge base of zkSync gotchas |
cast_abi_encode | cast abi-encode |
cast_abi_decode | cast abi-decode |
cast_calldata_decode | cast calldata-decode |
cast_call | cast call for read-only contract interaction |
cast_send | cast send for state-changing transactions |
cast_balance | cast balance for ETH balance queries |
cast_nonce | cast nonce for transaction nonce queries |
get_zksync_docs | Look up foundry-zksync documentation by topic |
anvil_zksync | Start or check a local anvil-zksync dev node |
foundryup-zksync)No install needed β run directly with npx:
Or add to claude_desktop_config.json / ~/.claude.json:
Then register with Claude Code:
All signing tools (deploy, cast_send, run_script) support multiple wallet methods. Choose based on your security needs:
For local dev with well-known test keys, use privateKey directly:
These are the default anvil-zksync test accounts β they hold no real value.
Warning: Never use
privateKeywith keys that hold real funds. MCP tool parameters are visible to the AI assistant and may be logged.
Keys are encrypted on disk β only the account name travels through MCP.
Then use account: "deployer" in any signing tool. Forge will prompt for the password at runtime, or you can point to a password file with passwordFile.
If you have an existing encrypted keystore JSON file (e.g. from Geth, MetaMask export):
| Method | Key Exposure | Best For |
|---|---|---|
| Hardware wallet | None (key never leaves device) | High-value production |
| Cloud KMS | None (key in HSM) | Automated production |
Named keystore (account) | None through MCP (encrypted on disk) | General production use |
| Keystore file | None through MCP (encrypted on disk) | Existing workflows |
privateKey | Visible to AI assistant | Local dev with test keys only |
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/foundry-zksync)<a href="https://allmcps.com/mcp/foundry-zksync"><img src="https://allmcps.com/api/badge/foundry-zksync?style=directory" alt="Foundry Zksync on AllMCPs" /></a>