@mcp-b/extension-tools wraps Chrome Extension APIs as MCP tool classes. Each API is a dedicated class that handles permission checking, error formatting, and tool registration against an McpServer instance.
Installation
Minimal example
Usage
Register tool classes in your Chrome extension’s background script:- An
McpServerinstance - An options object where each key corresponds to a tool method. Set a key to
trueto register that tool, orfalse(or omit it) to skip it.
BaseApiTools
All API tool classes extendBaseApiTools<TOptions>:
Available API tool classes (62)
Each class name follows the pattern<ApiName>ApiTools. The table below lists all implemented classes grouped by category.
Core browser
Content and scripting
Storage and data
Network
Downloads and capture
UI and interaction
DevTools
Identity and auth
System
Extension management
Media and output
Internationalization and messaging
Enterprise and platform
DOM extraction
Chrome API registry
TheChromeApi enum and CHROME_API_REGISTRY constant map every Chrome Extension API to its metadata:
Permission requirements
Declare required permissions in your extension’smanifest.json. APIs like i18n, runtime, and extension work without explicit permissions. Enterprise APIs require force-install via enterprise policy.
APIs under development (12)
The following APIs are not yet implemented:AccessibilityFeatures, Action, DevtoolsPerformance, DevtoolsRecorder, Dns, Events, ExtensionTypes, PrinterProvider, Privacy, Processes, SystemDisplay, Types.
Related
- @mcp-b/smart-dom-reader (DOM extraction used by
DomExtractionTools) - @mcp-b/transports (browser MCP transports)
- Chrome DevTools MCP (upstream DevTools Protocol bridge)
