Oh My Etch
Buy Now
ComponentsFacetsWooPatterns
IDEtch
IDEtch StarterIDEtch MCP
Stripe-like navigationFacet SystemMap FacetWoo Store
DocsPricingMy accountBuy Now
Etch Agent Bridge

Agentic Etch on the live builder.

Not another AI product. A local MCP server and Chrome extension that connect your existing harness to window.etch on a deployed WordPress site – the extension tracks the active tab for you.

Get Full + IDEtchSee MCP tools
Bring your own harness

If it speaks MCP, it works.

Claude Code, Codex, Cursor, OpenCode, Windsurf, and whatever comes next all launch the same local stdio MCP server. Your harness provides the model. The bridge only connects it to Etch.

CodexClaude CodeCursorCopilotOpenCodeWhatever comes next
Setup

Four steps. All local.

Install the extension once, open an authenticated Etch builder with the magic query flag, and point your harness at the MCP server.

Build

Run bun install and bun run build in the Etch Agent Bridge package. Reload the unpacked extension after each build.

Load

Load apps/extension/dist as an unpacked Chrome extension. Keep it installed while you use MCP agents.

Activate

Open the Etch builder on staging or production and add ?etch=magic to the URL. The extension ignores pages without it.

Connect

Add one MCP server entry to your harness config. The first client starts the local relay on port 8787.

Tool coverage

45 Etch MCP tools.

Validated pass-through to the Etch Public API: inspect, navigate, mutate blocks, styles, and global stylesheets, manage components and loops, undo/redo, and save only when you ask. Payloads are schema-checked against the official etch-public-api types before they reach the builder – malformed input returns a structured error in the same tool response, no browser round-trip.

targets

Targets & status

  • etch_list_targets
  • etch_get_active_target
  • etch_set_active_target
  • etch_get_status
  • etch_get_last_apply_result
blocks

Blocks

  • etch_get_selected_block
  • etch_get_document_tree
  • etch_get_block_json
  • etch_find_blocks
  • etch_insert_blocks
  • etch_replace_block
  • etch_update_block
  • etch_mutate_block_attributes
  • etch_duplicate_block
  • etch_move_block
  • etch_delete_block
styles

Styles

For selector-scoped CSS. For root-level CSS (@keyframes, @property, @font-face, utility classes) see Stylesheets below.

  • etch_list_styles
  • etch_apply_style_patch
  • etch_delete_style
  • etch_get_style_variable
  • etch_remove_style_variable
stylesheets

Stylesheets

For root-level CSS: @keyframes, @property, @font-face, utility classes, miniframework, root variables. Persists immediately.

  • etch_list_stylesheets
  • etch_get_stylesheet
  • etch_create_stylesheet
  • etch_update_stylesheet
  • etch_append_stylesheet
  • etch_delete_stylesheet
components

Components

  • etch_list_components
  • etch_get_component_json
  • etch_upsert_agent_component
  • etch_delete_agent_component
navigation

Navigation

  • etch_list_posts
  • etch_list_templates
  • etch_open_post
  • etch_open_template
  • etch_get_navigation_context
loops

Loops

  • etch_list_loops
  • etch_upsert_loop
  • etch_delete_loop
  • etch_bind_loop_to_block
history

History & UI

  • etch_undo
  • etch_redo
  • etch_get_color_scheme
  • etch_set_color_scheme
save

Save

  • etch_save_document

Mutations apply to the Etch canvas immediately but do not persist until you explicitly call etch_save_document. Use etch_undo to roll back. Component upserts/deletes and stylesheet mutations persist immediately through their respective APIs – there is no separate save step for those.

Local & intentional

No cloud. No model keys. Opt-in tabs only.

  • Stdio MCP server and WebSocket relay stay on 127.0.0.1 – nothing leaves your machine.
  • The bridge never asks for WordPress credentials. Your browser session is the auth layer.
  • Extension activates only on Etch builder URLs with ?etch=magic.
  • Multiple MCP clients can share one extension via the relay – one active canvas at a time.
Part of Oh My IDEtch

Starter builds the repo. Bridge keeps the agent on deploy.

Use the Git-first starter for local project code, then switch to Etch Agent Bridge when you need the same harness on a live builder tab – staging, production, or a client site.

See the starterPackage overview
src/Site/** in GitPHP builders + skillsMCP + extensionDeployed Etch tab
Included in IDEtch

Starter and bridge ship together.

Oh My IDEtch bundles both halves of the agentic Etch workflow. Add OME Full for components, patterns, facets, Woo, and the complete build stack.

Get Full + IDEtch