Practical overview
When it fits
Use it when an MCP-connected LLM assistant needs access to Foundry-based Solidity development or on-chain operations, especially when combining a persistent Forge workspace with local Anvil or RPC-backed contract work.
Who it is for
- Solidity developers who want an MCP client to access Foundry tools.
- Developers building LLM-assisted contract analysis or blockchain-query workflows.
- Users who work with local Anvil instances or remote RPC endpoints and can configure the required toolchain.
Documented uses
- Create and edit Solidity files in a persistent Forge workspace, install dependencies and run Forge scripts.
- Read contract state and blockchain information, retrieve receipts and logs, and inspect transaction traces.
- Use Cast operations for EVM tasks such as contract calls, balance checks, storage reads, gas estimates and unit conversions.
- Analyze bytecode and calldata through Heimdall-rs, including disassembly, decoding, decompilation and control-flow graphs.
- Deploy contracts or send contract transactions when the required signing key is configured.
Requirements & limits
The project is an open-source public GitHub repository under the MIT license. The README documents npm/npx installation and client configuration; it lists Node.js 18+ and Foundry tools as requirements. Heimdall-rs is required for smart-contract analysis. No account or price terms are specified in the provided project documentation.
- An MCP client must be configured to use the server; this is not presented as a standalone graphical Solidity IDE.
- Forge, Cast and Anvil must be installed, and Node.js 18 or later is required.
- Heimdall-rs is an additional requirement for the bytecode and transaction-analysis functions.
- RPC_URL is optional and provides a default endpoint; remote network access uses an RPC endpoint.
- PRIVATE_KEY is optional overall but needed to send transactions; the README advises against keys holding mainnet funds.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure the npm package in an MCP client
Install the server through npx and add it as an MCP server in a supported client.
Before you start
- Node.js 18 or later
- Foundry toolchain: Forge, Cast and Anvil
- An MCP client, such as Claude Code, Cursor, Claude or Windsurf
- Heimdall-rs if using smart-contract analysis tools
Steps
Run the documented npx command: npx @pranesh.asp/foundry-mcp-server.
Add an MCP server entry in the client configuration, using command npx and the package name as its argument.
Set RPC_URL if a default RPC endpoint is needed; set PRIVATE_KEY only if transaction sending is required.
Expected outcome
The MCP client is configured to access the server’s Foundry tools; the server maintains a persistent Forge workspace at ~/.mcp-foundry-workspace.
Guide limitations
- The README does not provide a verification procedure for confirming the client connection.
- PRIVATE_KEY is needed for sending transactions, not for the documented read-only contract calls.
- The README cautions against using keys holding mainnet funds and recommends testing or development use.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- PraneshASP/foundry-mcp-server · Official homepage title · retained in its source language

