Skip to main content
Glama
Jrigada

foundry-zksync-mcp

by Jrigada

deploy

Deploy a contract to a zkSync network using forge create. Get contract address, transaction hash, and deployer details.

Instructions

Deploy a contract to a zkSync network (forge create --zksync). Returns structured output with contract address, tx hash, and deployer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesAbsolute path to the foundry project directory
profileNoFoundry profile to use (maps to FOUNDRY_PROFILE env var). Selects a [profile.<name>] section from foundry.toml, e.g. 'zksync', 'ci', 'production'.
contractPathYesContract identifier in the form src/MyContract.sol:MyContract
rpcUrlYesRPC URL of the target zkSync network
privateKeyNoRaw private key for signing. Only use for local development with well-known test keys (e.g. anvil-zksync accounts). For production, use 'account' (named keystore) or hardware wallets instead.
accountNoNamed keystore account from ~/.foundry/keystores (recommended for production). Create one with: cast wallet import <name> --interactive
keystoreNoPath to an encrypted keystore JSON file
passwordFileNoPath to a file containing the keystore password
keystorePasswordNoKeystore password (prefer passwordFile to keep it out of process args)
unlockedNoUse eth_sendTransaction with --from address (no local signing). For nodes that manage keys natively.
fromNoSender address, used with --unlocked or hardware wallets. Maps to --from for cast/deploy, --sender for forge script.
ledgerNoSign with a Ledger hardware wallet
trezorNoSign with a Trezor hardware wallet
awsNoSign with AWS KMS (requires AWS_KMS_KEY_ID env var)
gcpNoSign with Google Cloud KMS (requires GCP_PROJECT_ID, GCP_LOCATION, GCP_KEY_RING, GCP_KEY_NAME, GCP_KEY_VERSION env vars)
broadcastNoIf true, actually broadcast the deployment transaction on-chain. Without this, forge create runs in dry-run mode.
constructorArgsNoConstructor arguments, each as a separate string. Solidity types are ABI-encoded by forge, e.g. ['0xaddr', '100', 'hello']
verifyNoIf true, verify the contract on a block explorer after deployment
verifierUrlNoBlock explorer verification API URL (e.g. https://api-era.zksync.network/api)
extraArgsNoAdditional CLI flags, each as a separate array element
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description does not disclose behavioral traits such as side effects (gas costs), failure modes, or permission requirements. Only mentions return structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words, front-loaded with key action and result.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 20 parameters and no output schema, the description is extremely sparse. Does not explain the significance of broadcast, various signing methods, or verification step. Incomplete for a complex deployment tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for all 20 parameters. Description adds no additional meaning beyond what schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool deploys a contract to zkSync using 'forge create --zksync' and returns structured output with contract address, tx hash, and deployer. It distinguishes from sibling tools like compile, verify, and run_script.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Sibling tools include run_script and verify, but description does not explain selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jrigada/foundry-zksync-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server