Skip to main content
Access Extension.js documentation through two standard AI-accessible surfaces. This lets your editor and assistants answer questions from current documentation rather than outdated training data.
This page is about giving assistants the docs — answering “how do I…” from current content. To let an assistant drive the tooling (run a dev session, stream logs, inspect the DOM, trigger an action, reload), see the separate control server in Chrome DevTools MCP with Extension.js.

​
Hosted MCP (Model Context Protocol) server

The docs site exposes a Model Context Protocol server at:
Point any MCP-compatible client at this URL and it gains tools to search the docs, fetch specific pages, and answer questions from current content.

​
One-click install

ClaudeCursorVS CodeChatGPT
Each page has a contextual menu (top-right of the page) with install buttons for common clients: Claude, Cursor, VS Code, and ChatGPT. Use those for the shortest path.

​
Manual install

After installing, ask your assistant something like “How do I configure browser-specific manifest fields in Extension.js?” The assistant consults the MCP tools and cites docs pages.

​
llms.txt

The documentation provides a static, machine-friendly index at: Use these when you want to feed the docs directly into a retrieval pipeline or summarize them in a custom agent. Extension.js regenerates them on every docs deploy.

​
Per-page AI actions

The page-level contextual menu also offers:
  • Copy page: copies the current page as Markdown for pasting into chats
  • View as Markdown: opens the raw Markdown source in a new tab
  • Ask ChatGPT / Claude / Perplexity: opens the respective assistant pre-loaded with the page as context

​
Agents that drive the CLI

The surfaces above answer questions from the docs. When your agent should operate the tooling itself, point it at two other resources:
  • Driving the CLI: the playbook for agents that run extension commands. It covers the capabilities handshake, machine output, the runtime attached gate, and the act verbs.
  • Machine contracts: the stable shapes those agents parse. ready.json, the schema-1 result envelope, the error-code table, the lifecycle frame stream, and the control bridge.
The CLI is also self-describing: extension --ai-help --output json prints its commands, flags, and contract paths as one JSON document.

​
Best practices

  • Prefer the MCP server when you want the assistant to reason across multiple pages and keep answers current.
  • Prefer llms-full.txt for offline tooling, evaluations, or custom RAG (retrieval-augmented generation) pipelines.
  • Use the per-page actions for quick spot questions about the page you are already reading.