Skip to main content
Glama
austintgriffith

eth-mcp

stack_start

Start local Ethereum development components: Anvil fork, contract deployment, and frontend dev server for free testing on localhost.

Instructions

Start one or more stack components for LOCAL development.

Components:

  • fork: Start LOCAL Anvil fork of the chain configured during stack_init (chainId 31337) RUNS: yarn fork --network Example: If you initialized with chain "base", this runs: yarn fork --network base Anvil understands chain names and resolves them to RPC URLs automatically. This creates a local copy of mainnet state - all testing happens here for FREE.

  • deploy: Deploy contracts to the LOCAL fork (NOT to mainnet!) This is safe and costs nothing - iterate as many times as needed.

  • frontend: Start the Next.js dev server connected to the local fork

IMPORTANT: All deployment via this tool goes to localhost:8545 (the local fork). This is the development workflow - test everything locally before mainnet.

For MAINNET deployment (after testing):

  1. yarn generate - Create deployer wallet

  2. yarn deploy --network - Deploy to real mainnet

You can start multiple components at once. Order matters: fork should start before deploy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentsYesComponents to start: fork, deploy, frontend
Behavior5/5

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

Without annotations, description fully explains behavior: fork creates local anvil fork, deploy is safe to localhost, frontend starts dev server; mentions ordering and that all testing is free.

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

Conciseness4/5

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

Well-structured with bullet points and sections, but slightly lengthy; however, every sentence adds value. Front-loaded with purpose.

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

Completeness5/5

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

Given no output schema, description fully covers what each component does and prerequisites (stack_init), making it complete for a development tool.

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

Parameters5/5

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

Adds significant value beyond schema: explains each enum option with examples (e.g., 'yarn fork --network base') and notes ordering dependency, though schema coverage is 100%.

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?

The description clearly states the tool starts stack components for LOCAL development, listing specific components (fork, deploy, frontend) and distinguishing it from siblings like stack_stop.

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

Usage Guidelines5/5

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

Explicitly says when to use (local development) and when not to (mainnet), provides alternative workflow for mainnet via yarn commands.

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/austintgriffith/eth-mcp'

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