extension.dev valid

Extension.dev platform documentation

Extension.dev is the hosted platform that takes a finished browser extension from build to every browser's store. These docs cover the console, the publish rail, shared previews, and the agent tools: the MCP server, the agent skill, and the CLI.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:52:09.966Z. Cached copy · Source on extension.dev

# Extension.dev platform documentation

> Extension.dev is the hosted platform that takes a finished browser extension from build to every browser's store. These docs cover the console, the publish rail, shared previews, and the agent tools: the MCP server, the agent skill, and the CLI.

Extension.dev sponsors Extension.js, the open source framework it builds on. The framework covers create, develop and build on your own machine, up to packaging, and is documented at https://extension.js.org. The platform begins where a workspace or an access token is minted, and that is what these docs describe.

extension.dev is not open to the public yet. Every page here is truthful about the platform. Signup and the hosted console answer that they are not open yet until it opens.

## Start here

What the platform is, and your first extension shipped to every browser.

- [Overview](https://docs.extension.dev): What Extension.dev is, the map of the docs, and where to go next.

## Agent tools and the CLI

What the platform gives a coding agent, and where the CLI mints a token.

- [MCP server](https://docs.extension.dev/tools/mcp): Give a coding agent the build, preview, release and publish verbs.
- [Server flags and telemetry](https://docs.extension.dev/tools/mcp/flags): The three flags that decide which MCP tools an agent sees, the approvals that wait for a person, the fence around page-written text, and the one telemetry event.
- [Platform tools](https://docs.extension.dev/tools/mcp/platform): Log an agent in to extension.dev, create several projects under one approval, share a build in progress, and keep publish and submit apart with the eleven platform tools.
- [Run on Safari](https://docs.extension.dev/tools/mcp/safari): Start a Safari dev session from an agent, turn on the one Safari setting it needs, and see which MCP tools work there and which Extension.js version each one needs.
- [Agent skill](https://docs.extension.dev/tools/skill): The judgment half of the agent stack, one skill in the open Agent Skills format.
- [Pair with Chrome DevTools MCP](https://docs.extension.dev/tools/chrome-devtools-mcp): Run Google's chrome-devtools-mcp and the extension.dev MCP server in one agent config, and know which one to reach for.
- [CLI](https://docs.extension.dev/tools/cli): The Extension.js command line, and the agent-facing package that reaches the platform.
- [Agent bridge](https://docs.extension.dev/tools/agent-bridge): The local channel that lets a terminal, a script or an AI agent observe a running extension and, per session, act on it.
- [Agent logs](https://docs.extension.dev/tools/logs): One ordered stream of everything the extension does, across every context, written to a local file and readable from the terminal or an agent.
- [Inspect and act](https://docs.extension.dev/tools/inspect-and-act): Read the live DOM of any surface and run scoped operations in the exact extension context you care about, on Chrome and Firefox.

## MCP tool reference

One pa
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=extension.dev · GET /v1/domain/extension.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for extension.dev:
1. POST https://agentwebmap.com/v1/sites/extension.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://extension.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/extension.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/extension.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.