@extension.dev/mcp, a Model Context Protocol server, and @extension.dev/skill, an agent skill. Both are extension.dev products with their own repositories and documentation. They work with any Extension.js project. The server wraps the extension CLI and the local control channel that extension dev opens. An agent can then build, run, inspect and reload your extension in a real browser, with the same gates that the CLI enforces.
Extension.js itself is the framework and the CLI. Nothing in it depends on the agent tooling, and every operation that the server exposes is also a CLI verb. See Debugging.
Install
Where the documentation lives
- MCP server: install, the tool list, session gates and login.
- Agent skill: what the skill teaches an agent and how to install it.
- Run beside Chrome DevTools MCP: which server to reach for, and how to install both.
Next steps
- Chrome DevTools MCP: Google’s Chrome debugging server as an integration.
- Driving the CLI: the agent playbook for the CLI itself, no MCP required.
- AI access via MCP and llms.txt: give your assistant the docs.