A switchboard for AI in your browser: wire in any model, script WebMCP tools, connect remote MCP servers, bring your commands.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"github": {
"url": "https://your-mcp-server.com/mcp",
"transport": "http"
},
"company-tools": {
"url": "https://internal.example.com/mcp",
"authToken": "your-bearer-token",
"transport": "http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A switchboard for AI in your browser: wire in any model, script WebMCP tools, connect remote MCP servers, bring your commands.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / browser
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
Browser automation with Puppeteer for web scraping and testing
Dynamic problem-solving through sequential thought chains
MCP Security Weekly
Get CVE alerts and security updates for AgentBoard and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A switchboard for AI in your browser: wire in any model, script WebMCP tools, connect remote MCP servers, bring your commands.
/analyze, not paragraphs.Bring your own models—local, fine-tuned, custom—to power multiple agent profiles. Connect remote MCP servers: bring external tools (APIs, databases, services) into browser context. Script WebMCP tools that interact with page content — think, Greasemonkey for the AI age. Built for power users.
┌────────────────────────────────────┐
│ === Tab-Scoped AI Sidebar === │
│ - Markdown rendering │
│ - Tool visualization │
│ - Reasoning display │
└────────────┬───────────────────────┘
│ Port (streaming)
┌────────────▼───────────────────────┐
│ Background Service Worker │
│ ┌──────────────────────────────┐ │
│ │ AI Client │ │
│ │ - Multi-provider │ │ ┌──────────────────────────┐
│ │ - Streaming + tools │ │ │ Browser Tab │
│ └──────────────────────────────┘ │ │ ┌────────────────────┐ │
│ ┌──────────────────────────────┐ │ │ │ ISOLATED: Relay │ │
│ │ ToolRegistry │ │◄─────┤ │ - Forwarding │ │
│ │ - WebMCP + Remote + System │ │ Port │ └────────┬───────────┘ │
│ └──────────────────────────────┘ │ │ │ │
│ ┌──────────────────────────────┐ │ │ ┌────────▼───────────┐ │
│ │ TabManager │ │ │ │ MAIN: window.agent │ │
│ │ - Script injection │ │ │ │ - Tool execution │ │
│ │ - Lifecycle │ │ │ │ - Full DOM access │ │
│ └──────────────────────────────┘ │ │ └────────────────────┘ │
└────────────────────────────────────┘ └──────────────────────────┘
The AI sidebar is tab-scoped—each sidebar instance binds to one browser tab and sees tools from that tab's page context plus global tools (remote MCP servers and system capabilities). When you open the sidebar, the background service worker injects WebMCP scripts into the page: a polyfill that provides window.agent, a relay in the ISOLATED world, and a bridge in the MAIN world. Pages register tools via window.agent.registerTool(), triggering tools/listChanged events that flow through a persistent port connection from the relay to the background service worker. The ToolRegistry aggregates all discovered tools—WebMCP from pages, remote MCP from external servers, system tools from the extension—and converts them to AI SDK format for the AI Client.
When you send a message, the AI Client streams responses from your chosen provider (OpenAI, Anthropic, Google, or custom endpoint). Tool calls route based on type: WebMCP tools execute in the browser tab's MAIN world via JSON-RPC callTool commands (full DOM access, zero serialization overhead), remote MCP tools execute on your external servers with streaming HTTP, and system tools run in