extension_docs_search
Find the docs page to cite before answering any question about a WebExtension API, a manifest key, a permission, or a difference between Chrome, Firefox, Edge and Safari.
Quick start
How does Firefox handle the sidebar API? Search the docs before you answer
Asked a cross-browser question, the agent searches the docs before answering.
How the agent uses it
It searches the Extension.js and extension.dev docs (free, no login) and answers with the pages, each with its URL and an excerpt. Memory is the fallback only when it returns nothing.
Reference
| Group | local, on by default |
| Tier | Create and build |
| Needs | none |
| Read only | yes |
| Destructive | no |
| Idempotent | yes |
| Reaches the open web | yes |
Inputs
| Input | Type | Required | Default | What it does |
|---|---|---|---|---|
query | string | yes | What to look up, in a few words. | |
limit | number | no | 5 | How many pages to return, 1 to 8. |
api | string | no | Platform base URL (default EXTENSION_DEV_API_URL, else https://www.extension.dev) |
When it fails
- The answer depends on the network. This tool reaches the open web, so a refusal can be the network, not the project.
Next
- MCP server: install, the two groups and the session gates
- Install in your client
extension_add_feature: Plan the surface before adding an options page, a popup, a side panel, a content script, a devtools panel, a new tab page or a background script to an existing extension.extension_build: Build a browser extension for production.extension_create: Create a browser extension project from a template in the extension.dev catalog.extension_templates: Browse the extension.dev template catalog.