@mcp-b/extension-tools packages Chrome Extension APIs as MCP tool classes. It is the package to use when you are writing a Chrome extension and want to expose tabs, bookmarks, history, storage, or scripting capabilities to an MCP client.
When to use this package
- You are building an extension background script or related extension runtime.
- You want prebuilt tool classes instead of manually wrapping Chrome APIs.
- You need extension-specific capabilities that a webpage runtime cannot provide.
When not to use this package
- You are exposing tools from a normal webpage. Use
@mcp-b/globalor@mcp-b/webmcp-polyfill. - You need DOM extraction only. Use
@mcp-b/smart-dom-reader.
Where it sits in the package graph
This package is part of the tooling layer rather than the page runtime stack. Some classes depend on@mcp-b/smart-dom-reader for DOM-focused extraction behavior.
First step
Create an MCP server in your extension runtime, then register only the tool classes you want to expose. The reference page groups the API tool classes and their option surfaces.Related pages
Reference
Tool classes, option tables, and extension integration details.
@mcp-b/smart-dom-reader overview
DOM extraction utility used by several extension workflows.
@mcp-b/chrome-devtools-mcp overview
Alternative tooling when you want a DevTools bridge instead of an extension.
Framework guide
Runtime guidance for webpage-facing packages when you are not in an extension context.