Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Expose foundry-zksync (forge, cast, anvil-zksync) tools for zkSync Era development
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"foundry-zksync": {
"command": "npx",
"args": [
"-y",
"foundry-zksync-mcp"
]
}
}
}Run this in your terminal
claude mcp add foundry-zksync -- npx -y foundry-zksync-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"foundry-zksync": {
"command": "npx",
"args": [
"-y",
"foundry-zksync-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"foundry-zksync": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"foundry-zksync-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Jrigada, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.3) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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:
claude mcp add foundry-zksync -- npx -y foundry-zksync-mcp
Or add to claude_desktop_config.json / ~/.claude.json:
{
"mcpServers": { "foundry-zksync": { "command": "npx", "args": ["-y", "foundry-zksync-mcp"] } } }
git clone https://github.com/Jrigada/foundry-zksync-mcp.git
cd foundry-zksync-mcp npm install npm run build
Then register with Claude Code:
claude mcp add foundry-zksync node /absolute/path/to/foundry-zksync-mcp/dist/index.js
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:
privateKey: "0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80"
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.
# Import a private key into a named keystore (interactive, key never shown)
cast wallet import deployer --interactive
ls ~/.foundry/keystores/
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):
keystore: "/path/to/keystore.json"
passwordFile: "/path/to/password.txt"
ledger: true # Ledger
trezor: true # Trezor
aws: true # AWS KMS (set AWS_KMS_KEY_ID env var)
gcp: true # Google Cloud KMS (set GCP_PROJECT_ID, GCP_LOCATION, etc.)
| 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 |
src/
index.ts MCP server entry point, registers all 21 tools knowledge.ts Knowledge base (45+ entries) and system addresses tools/ shared.ts Profile field and env builder shared across forge tools init.ts forge init with zkSync config compile.ts forge build --zksync test.ts forge test --zksync run_script.ts forge script --zksync deploy.ts forge create --zksync (structured output) verify.ts forge verify-contract --zksync install.ts forge install clean.ts forge clean gas_report.ts forge test --gas-report snapshot.ts forge snapshot read_foundry_toml.ts Read project config explain.ts Error/log explanation with knowledge base get_zksync_docs.ts Documentation lookup with embedded content cast_abi_encode.ts cast abi-encode cast_abi_decode.ts cast abi-decode cast_calldata_decode.ts cast calldata-decode cast_call.ts cast call cast_send.ts cast send cast_balance.ts cast balance cast_nonce.ts cast nonce anvil_zksync.ts anvil-zksync node management tests/ 133 tests (vitest)