Introducing MCP‑B

Model Context Protocolfor the Browser

Today’s AI automation is like using a robot to read your screen and click buttons. MCP‑B lets assistants call your site’s real functions instead.

Add ~50 lines of code and your website becomes AI‑ready with zero configuration.

No API keys or OAuth — uses your logged‑in session.

Tab • store.example.com
Secure MCP channel
Action
Add to cart
  • • Product: “Trail Shoes”
  • • Quantity: 1
  • • Size: 10
Call result
Added to cart ✓
Trail Shoes • Qty 1 • Size 10
Runs with your logged‑in session
Executes with the user's session
Why MCP‑B?

The bridge between your appandAI assistants

Your Website
Expose context and tools
addToCart
Add a product to the user’s active cart
product
Trail Shoes
size
10
quantity
1
notes
Uses browser session (no API keys)

Define what the assistant can see and do.

AI Assistants
Secure tool calls, structured output
// Example MCP tool call
await mcp.callTool({ name: 'createInvoice', arguments: { items } })
// Runs with the user's session, not new auth
Works across any site or frameworkUp and running in minutes
How it flows

From request to result — securely

AI Assistant
“Add to cart”
MCP‑B
Routes tool call
Your Website (tab)
Executes with session
Your APIs
No new auth needed

End‑to‑end over a secure channel • No API keys • Pixel‑accurate actions

Live Demo

See MCP-B in Action

Watch how the MCP-B AI assistant seamlessly interacts with an MCP-B enabled website — no API keys, no OAuth, just pure productivity.

Demo
Live Recording
2 min demo
Real-time AI automation

Instant Execution

Tasks complete in milliseconds

Secure by Default

Uses existing browser auth

Zero Config

Works out of the box

Browser‑Native MCP

Why MCP-B Changes Everything

While other solutions take 10-20 seconds per action and cost $4-5 per task, MCP-B delivers instant results with zero configuration. The future of browser automation is here.

The Breakthrough

Browser-Native MCP Servers

Instead of running MCP servers as separate processes or cloud services, we embed them directly into web pages. The MCP server becomes part of your web application.

The Challenge

  • Remote MCPs need complex OAuth 2.1
  • Local MCPs require API keys everywhere
  • White-collar work happens in browsers

Our Solution

  • Run MCP servers inside web pages
  • Use existing browser authentication
  • Bridge to any MCP client via extension

The Result

  • Authentication just works
  • No API keys or OAuth flows
  • Works with any website

10,000x Performance Improvement

Traditional browser automation performance:

  • • 10-20 seconds per task
  • • $4-5 in API costs per simple action
  • • Multiple model calls for UI parsing
  • • Brittle, unreliable execution

MCP-B executes the same tasks in milliseconds with direct API calls.

Authentication That Actually Works

Why MCP-B solves auth elegantly:

  • • Uses your existing browser sessions
  • • No OAuth 2.1 implementation needed
  • • No API keys to manage or distribute
  • • Respects existing permission models

Your existing APIs work out of the box — the browser handles everything.

How MCP-B Works: From Web Page to AI Assistant

1. Tab MCP Servers

Your Web Apps

Tab MCP Server

• TypeScript, in-memory transport

• Wraps your authenticated APIs

• Uses existing cookies/JWT

fetch/XHR

Your Existing APIs

• No changes needed

• Same auth as UI

2. MCP-B Extension

Chrome Extension

Content Scripts

Connect to tab servers via postMessage

MCP Hub (Service Worker)

• Aggregates all tab tools

• Routes tool calls

• Manages connections

Built-in Chat UI

Side panel AI assistant

3. MCP Clients

AI Assistants

Native Bridge

• Native messaging tunnel

• Proxy server option

Claude Desktop
Cursor IDE
Cline / Others

Complete flow: AI requests tool → Extension routes to tab → Tab MCP executes using your auth �� Results flow back to AI

MCP servers run in web pages, extension bridges to AI clients, transport layers handle the plumbing

Incredibly Simple Setup

No OAuth flows, no API keys, no complex configuration. Just ~50 lines of code and your website becomes AI-ready in minutes, not days.

For Developers

Add MCP to Your Website in Minutes

1

Install the package

bash
npm install @mcp-b/transports @modelcontextprotocol/sdk
2

Create your MCP server

typescript
import { TabServerTransport } from '@mcp-b/transports';
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
import { z } from 'zod';

const server = new McpServer({
  name: 'invoice-system',
  version: '1.0.0'
});

server.tool('createInvoice', 'Create a new invoice', {
  customerEmail: z.string().email(),
  items: z.array(z.object({
    description: z.string(),
    amount: z.number()
  }))
}, async ({ customerEmail, items }) => {
  // This is just a normal fetch to your existing API
  const response = await yourPreAuthorizedApiClient('/api/invoices', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ customerEmail, items })
  });

  if (!response.ok) {
    throw new Error(`Failed to create invoice: ${response.statusText}`);
  }
  // You get full control over what the model get's to know about the response
  return { content: [{ type: 'text', text: JSON.stringify(await response.json())  }] };
});

const transport = new TabServerTransport();
// This server is now callable by the mcp-b chrome extension
await server.connect(transport);
3

That's it! 🎉

Your MCP server automatically uses your existing authentication. When users with the MCP-B extension visit your site, their AI assistants can now interact with your APIs using their active session.

No API Keys

Uses browser's existing authentication

Type-Safe

Full TypeScript support with Zod validation

Secure by Default

Respects your existing permissions

For Users

Even Simpler for End Users

1

Install Extension

One-click install from Chrome Web Store. No configuration needed.

2

Start Using AI

Visit any MCP-enabled website. Your AI assistant automatically gains access.

No API keys to manage. No OAuth to configure. It just works.

Better for AI, Better for Users

See how MCP-B compares to existing approaches

How MCP-B Compares to Existing Approaches

Traditional Approach

Browser Automation

Screen Scraping

• AI analyzes screenshots

• Clicks visual elements

• Breaks with UI changes

Result: Brittle & Slow

Current State

Traditional MCP

API Keys Required

• Separate auth per service

• Complex credential mgmt

• Technical setup needed

Result: High Barrier

The Future

MCP-B Bridge

Direct API Access

• Uses browser sessions

• Structured data access

• Zero configuration

Result: Works Instantly

Traditional Browser Automation

Visual Parsing = Poor Performance

  • AI must parse screenshots and visual elements
  • Breaks when UI changes
  • Slow and error-prone
  • Requires complex selectors and wait logic
MCP-B Structured Access

Direct API Access = Reliability

  • Direct access to structured data and APIs
  • UI changes don't affect functionality
  • Fast and accurate execution
  • Clean, semantic tool definitions

Built for Real-World Use

MCP-B solves the fundamental problems that have prevented AI from working with web applications

Lightning Fast Performance

Direct API calls in milliseconds vs 10-20 seconds for screen scraping automation.

Zero Configuration

Add ~50 lines of code to your website. No OAuth flows, no API keys, no complex setup.

Cross-Application Workflows

AI seamlessly works across multiple sites using each site's existing permissions.

Extensible Platform

Acts as an MCP hub that other AI extensions can connect to and extend.

Secure by Design

MCP server is part of your app, running your code, respecting your access controls.

Authentication Just Works

Uses existing browser sessions. No OAuth 2.1 complexity, no API keys to manage.

MCP-B Browser Extension

AI-powered browser assistant with Model Context Protocol integration

Now Available

One Extension, Unlimited Possibilities

Transform your browser into an AI-powered workspace. The MCP-B extension brings the full power of Model Context Protocol directly to your browser.

MCP Hub for Extensions

Acts as an MCP of MCPs — other AI extensions can connect to MCP-B to access all browser tabs' tools.

Browser Automation

Let AI manage tabs, bookmarks, and interact with web pages through MCP.

Privacy First

All processing happens locally. Your data never leaves your device without permission.

Cross-Browser

Works with Chrome, Edge, and Firefox. One extension for all browsers.

Getting Started

  1. 1.Install from Chrome Web Store
  2. 2.Click extension icon to open side panel
  3. 3.Configure your AI provider
  4. 4.Start automating your workflows

By using the MCP-B Browser Extension, you agree to our Privacy Policy

Ready to Get Started?

The future of AI assistance isn't in complex OAuth flows or managed infrastructure. It's in the browser you already have open.

Community Driven
Cross-Browser