extension_templates
Browse the extension.dev template catalog.
Quick start
Which templates have a side panel? Show me the source of the best one
Asked what to start from, the agent lists the templates by surface and names the command.
How the agent uses it
Pass action:'list' (the default) to search and filter it and get metadata per template. Pass action:'source' with a slug to read one template's files, for learning a pattern before building something similar. Read framework as the UI framework only, never the language: TypeScript and JavaScript templates live under slugs ('typescript', 'content-typescript'), shadcn is a React variant ('sidebar-shadcn'), and provider AIs carry the 'ai' tag ('ai-chatgpt', 'ai-claude'). Reach those through query, tags or slug.
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 |
|---|---|---|---|---|
action | "list" | "source" | no | "list" | |
slug | string | no | source: which template to read (e.g. 'ai-claude', 'content-react'). Required for source. | |
files | array of string | no | source: paths to read (e.g. ['src/manifest.json']). Omit for the file listing. | |
query | string | no | list: keyword search over slug, description, tags and useCases. Ranks by word matches, so a natural phrase works. | |
surface | "content" | "sidebar" | "newtab" | "background" | no | list: filter by surface. For a popup/action starter use query:'action', not a surface. | |
framework | "react" | "vue" | "svelte" | "preact" | "" | no | list: UI framework filter (empty string = vanilla JS). | |
tags | array of string | no | list: filter by tags, e.g. ['ai', 'chat']. | |
featured | boolean | no | list: only featured templates. |
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_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.