Agent-ready Etch

Build in Git. Edit on deploy.

Oh My IDEtch is two products in one package: a code-owned starter for local agentic builds, and Etch Agent Bridge for the same harness on a live Etch builder tab.

Get Full + IDEtch See the package

Starter + MCP Bridge – Local only – Any MCP harness

oh-my-idetchPACKAGE

Oh My IDEtchstarter/mcp-bridge/skills/extension/

one harness

// local repo build
agent → src/Site/** → git diff

// deployed builder
agent → MCP → extension → window.etch

Your model. Your agent.Bridge connects. It does not replace.

2Products in one package

LocalMCP + relay + extension

39Etch MCP tools

AnyMCP-capable harness

What is in the package

Two ways to work. One agent stack.

Start in the IDE with Git-owned project code. After deploy, keep the same agent on the Etch builder – staging, production, or client site.

01 · Starter

Git-first local build

Code-owned src/Site/**, strict PHP builders, repo-local skills, before-we-start onboarding, and a local WordPress preview target – not a magic export box.

GitLocal wp-envBuild skillsAGENTS.md

Explore

02 · MCP Bridge

Agentic workflow on deploy

Local MCP server plus Chrome extension. Your harness controls the Etch builder on a deployed site – the extension tracks the active tab and exposes the full Etch Public API.

MCPExtension?etch=magic39 tools

Explore

etch-agent-bridgeLOCAL

Your agentClaude · Codex · Cursor · OpenCode
→
MCP serverstdio · local only
→
Relayws://127.0.0.1:8787
→
Extensionactive Etch tab
→
window.etchdeployed builder

Etch Agent Bridge

MCP relay connected

Active target: staging.example/wp-admin/…&etch=magic
Selected block: block-hero-01
Save state: idle

first promptUse Etch MCP tools to list targets and inspect the selected block. Do not save.

Complete package

Starter and bridge ship together.

Oh My IDEtch gives you the repo rails and the live-builder bridge. Pair it with OME Full for components, patterns, facets, Woo, and the full Etch build stack.

Get Full + IDEtch