extensions

Develop Chrome extensions and MCP tools with Manifest V3 and OAuth.

3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/brief-hq/brief-wiggum --skill extensions-brief-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extensions
Source: https://github.com/brief-hq/brief-wiggum/tree/main/.claude/skills/extensions
Command: npx skills add https://github.com/brief-hq/brief-wiggum --skill extensions-brief-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides patterns and guidance for developing Chrome extensions and Model Context Protocol (MCP) tools, enabling AI agents to interact with web browsers and external services.

Core Features & Use Cases

  • Chrome Extension Development: Covers Manifest V3, Side Panel architecture, OAuth authentication, and shared component usage with @briefhq/chat-ui.
  • MCP Tool Development: Details how to define, register, and test new MCP tools for AI agent interaction.
  • Use Case: Develop a custom Chrome extension that allows an AI agent to automatically fill out web forms using data from a user's CRM, or create an MCP tool that enables an AI to interact with a project management API.

Quick Start

Follow the local setup instructions to build and load the Chrome extension in your browser.

Frequently Asked Questions about extensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Chrome extension with the Side Panel API using Manifest V3?

Building a Chrome extension with the Side Panel API using Manifest V3 involves organizing components around Side Panel architecture, setting up OAuth authentication, and integrating shared UI components for browser interaction.

What is MCP tool development and how does it connect to AI agents?

MCP tool development defines, registers, and tests Model Context Protocol tools that enable AI agents to interact with web browsers and external project management or CRM APIs.

How do I implement OAuth with PKCE in a Chrome extension?

Implementing OAuth with PKCE in a Chrome extension requires defining specific authentication flows within the Manifest V3 architecture to securely authorize access to external services.

Can I use shared UI components when developing Chrome extensions?

Yes, developing Chrome extensions can utilize shared component usage with the @briefhq/chat-ui library to maintain consistent architectural patterns across the Side Panel interface.

What's the best way to test MCP tools for AI agent interaction?

Testing MCP tools for AI agent interaction involves applying specific testing strategies to verify the tool definition and registration processes before enabling external service automation.

Do I need Manifest V3 to build a Chrome extension with a Side Panel?

Yes, Manifest V3 is required to build a Chrome extension utilizing the Side Panel API, providing the necessary architectural patterns and component organization for modern browser integration.