Skip to content
For Agents

Run eth2-quickstart from an AI agent

eth2-quickstart is a repo-aware toolkit for Ethereum node operators: a packaged agent skill, a local MCP server, and a JSON-first ./scripts/eth2qs.sh CLI. An agent that clones the repo can bootstrap, operate, inspect, and clean a node stack using the same commands a human operator would run — without inventing a second toolchain.

What this is

  • A packaged skill — Anthropic skill-creator format, published via ClawHub, with 9 reference docs covering workflow, operator flows, safety, and sizing.
  • An MCP server — a thin stdio wrapper for Claude Code and Codex that calls ./scripts/eth2qs.sh directly; it does not reimplement install or operations logic.
  • A JSON CLI — the same wrapper exposes --json on doctor, plan, stats, validators, and more, for agents that would rather parse structured output than screen-scrape.

Install the skill

The skill is repo-aware: install it, then use it from inside aneth2-quickstartcheckout.

# once published to ClawHub
clawhub install eth2-quickstart

# GitHub-path fallback (Codex-style skill installer)
python ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
  --repo chimera-defi/eth2-quickstart --path skills/eth2-quickstart

Connect over MCP

For agent runtimes with native tool support, register the local stdio server and run the agent from inside the repo checkout so it can resolve the canonical wrapper.

python3 -m pip install mcp

# Claude Code
claude mcp add eth2-quickstart -- ./mcp_server/run_eth2qs_mcp.sh
# or: ./scripts/install_claude_eth2qs_mcp.sh

# Codex
codex mcp add eth2-quickstart ./mcp_server/run_eth2qs_mcp.sh

Canonical commands

Every command below has a machine-readable --json form. Prefer doctor and plan before any apply command.

# from an eth2-quickstart checkout
./scripts/eth2qs.sh doctor --json
./scripts/eth2qs.sh plan --json
./scripts/eth2qs.sh phase2 --execution=geth --consensus=prysm --mev=mev-boost
./scripts/eth2qs.sh validators --json

Safety contract

  • No validator keys are generated or removed by the agent layer — key generation happens on the node CLI (validator-deploy), never through MCP.
  • Human confirmation is required before root-required actions, reboot-causing steps, and destructive cleanup.
  • Funds-affecting validator operations are preview-only via MCP. The read-only tool eth2qs_validator_op_preview returns the exact node CLI command to run (exit, withdrawal-credential change, consolidation, EIP-7002 exit) — execution and confirmation always happen on the node CLI, never through MCP.
  • Cleanup preserves secrets. The data-purge flow is scoped to default data/state directories and is designed to preserve keys, keystores, wallets, and ~/secrets.

Learn more

llms.txt

Raw-ingest agent instructions, served on this site.

llms-full.txt

Expanded agent-facing summary of install, operation, and cleanup.

SKILL.md

The skill entrypoint: routing rules and the full reference set.

Validator management

Full guide to the validator lifecycle commands and the MCP preview contract.

Operating for a human?

The quickstart walks through the same two-phase install for people.

Get Started