| layout | default |
|---|---|
| title | MCP Chrome Tutorial |
| nav_order | 184 |
| has_children | true |
| format_version | v2 |
Learn how to use
hangwin/mcp-chrometo expose browser automation, content analysis, and semantic tab search tools to MCP clients.
MCP Chrome is a practical bridge between AI assistants and a user's real Chrome session. It avoids separate browser sandboxes and enables automation against active tabs, history, bookmarks, network events, and semantic content search.
This track focuses on:
- setting up native bridge and extension components correctly
- understanding streamable HTTP and stdio transport options
- using the 20+ tool surface safely and effectively
- operating troubleshooting, permissions, and release workflows
- repository:
hangwin/mcp-chrome - stars: about 10.8k
- latest release:
v1.0.0(published 2025-12-29)
flowchart LR
A[MCP Client] --> B[Native MCP server]
B --> C[Native messaging bridge]
C --> D[Chrome extension background]
D --> E[Chrome APIs and content scripts]
D --> F[Semantic/vector search engine]
| Chapter | Key Question | Outcome |
|---|---|---|
| 01 - Getting Started and Native Bridge Setup | How do I install and connect MCP Chrome reliably? | Working local baseline |
| 02 - Architecture and Component Boundaries | How do native server, extension, and AI layers fit together? | Strong system model |
| 03 - Tool Surface: Browser, Network, and Interaction | What can the tool API do across tabs and pages? | Better tool selection |
| 04 - Semantic Search and Vector Processing | How does semantic tab search work internally? | Higher signal retrieval |
| 05 - Transport Modes and Client Configuration | When should I use streamable HTTP vs stdio? | Stable client integration |
| 06 - Visual Editor and Prompt Workflows | How do visual workflows improve automation quality? | Faster iteration |
| 07 - Troubleshooting, Permissions, and Security | What usually breaks and how do we fix it safely? | Better operations |
| 08 - Contribution, Release, and Runtime Operations | How do teams maintain and extend MCP Chrome over time? | Long-term ownership |
- how to install and register MCP Chrome for daily AI workflows
- how to map tool calls to browser-native capabilities safely
- how to configure transport and client wiring across environments
- how to handle security, troubleshooting, and release management
- Repository
- README
- Architecture
- Tools Reference
- Troubleshooting
- MCP CLI Config Guide
- Visual Editor
- Changelog
- Chrome DevTools MCP Tutorial
- MCP Servers Tutorial
- MCP Inspector Tutorial
- Firecrawl MCP Server Tutorial
Start with Chapter 1: Getting Started and Native Bridge Setup.
- Start Here: Chapter 1: Getting Started and Native Bridge Setup
- Back to Main Catalog
- Browse A-Z Tutorial Directory
- Search by Intent
- Explore Category Hubs
- Chapter 1: Getting Started and Native Bridge Setup
- Chapter 2: Architecture and Component Boundaries
- Chapter 3: Tool Surface: Browser, Network, and Interaction
- Chapter 4: Semantic Search and Vector Processing
- Chapter 5: Transport Modes and Client Configuration
- Chapter 6: Visual Editor and Prompt Workflows
- Chapter 7: Troubleshooting, Permissions, and Security
- Chapter 8: Contribution, Release, and Runtime Operations
Generated by AI Codebase Knowledge Builder