1. Conduid
  2. AI
  3. Agentboard
MCP server · AI

Agentboard

A switchboard for AI in your browser: wire in any model, script WebMCP tools, connect remote MCP servers, bring your commands.

Unclaimed MIT last commit 6 months ago ai
77Good

Scored 3 hours ago · breakdown

About Agentboard

Agentboard is an MCP server published by igrigorik in the AI category: a switchboard for AI in your browser: wire in any model, script WebMCP tools, connect remote MCP servers, bring your commands. It has been installed 0 times through Conduid.

The repository has 109 stars and 16 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx agentboard

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Agentboard

Powered by Claude · Grounded in docs

I know everything about Agentboard. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.9.0AgentBoard v0.9.0 · 7 Aug 2026Install latest from [Chrome Web Store](https://chromewebstore.google.com/detail/agentboard/jlmajjfiibgnejlndfoboojahlclgoam?authuser=0&hl=en)**. Local workspace & memory support <img width="1888" height="1141" alt="SCR-20260806-tehf"…
v0.8.0AgentBoard v0.8.0 · 20 Jul 2026What's Changed Standardized WebMCP support on `document.modelContext`, with native Chromium integration when available. Improved tool reliability with tab/document scoping, duplicate-name protection, and cancellation during navigation.…
v0.7.3AgentBoard v0.7.3 · 18 Apr 2026What's Changed Handle ontoolchange alongside registerToolsChangedCallback (b83f582) gmail script v0.2 (667b922) Full Changelog**: https://github.com/OWNER/REPO/compare/v0.7.2...v0.7.3
v0.7.2AgentBoard v0.7.2 · 15 Apr 2026What's Changed fix: add Trusted Types policy for read_page on TT-enforcing sites (c473c55) Full Changelog**: https://github.com/OWNER/REPO/compare/v0.7.1...v0.7.2
v0.7.1AgentBoard v0.7.1 · 15 Apr 2026What's Changed per-message <site_tools> grounding + composable system prompt (ab87573) migrate toolchain from npm to pnpm (839869e) fix: downgrade no tab errors to debug (63acea3) clarify access scope in system prompt (7aa083e) Full…

README

AgentBoard

A switchboard for AI in your browser: wire in any model, script WebMCP tools, connect remote MCP servers, bring your commands.

  • Multi agent: Configure as many profile as you want, switch mid-conversation.
  • Your provider: OpenAI, Anthropic, Google, or your own completion-compatible endpoint.
  • Your settings: System prompts, temperature, thinking settings.
  • Your keys: Bring your own API keys. No lock-in, no upselling.
  • Your tools: Script WebMCP tools for page interactions. Connect remote MCP servers.
  • Your commands: Template prompts with arguments; type /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.

Install extension from Chrome Web Store


Architecture overview

  ┌────────────────────────────────────┐
  │  === 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 the service worker with elevated privileges (CORS-free fetching, for example).


Agent Profiles

Gemini with Extended Thinking:

{
  provider: "google",
  model: "gemini-2.0-flash-thinking-exp-01-21",
  apiKey: "your-api-key",
  systemPrompt: "You are a helpful assistant.",
  reasoning: {
    enabled: true,
    google: {
      thinkingBudget: 8192,
      includeThoughts: true
    }
  }
}

Local Ollama:

{
  provider: "openai",
  endpoint: "http://localhost:11434/v1",
  model: "llama3.1:70b",
  apiKey: "ollama",  // Required but not used
  systemPrompt: "You are a coding assistant.",
  temperature: 0.7
}

Configure as many profiles as you want. Switch mid-conversation.

MCP tools

Bring custom external tools to give your agent superpowers. AgentBoard supports remote MCP servers (must support HTTP streaming), and WebMCP-exposed tools. Better, it allows you to author and inject own WebMCP tools to script custom workflows that your agent can call to complete tasks on your behalf.

Remote MCP Servers

The agent can call any remote MCP server, as long as it supports HTTP streaming. Bring your MCP config and agent will do the rest to discover and expose available tools. Run /tools in chat to audit available capabilities.

{
  "mcpServers": {
    "github": {
      "url": "https://your-mcp-server.com/mcp",
      "transport": "http"
    },
    "company-tools": {
      "url": "https://internal.example.com/mcp",
      "transport": "http",
      "authToken": "your-bearer-token"
    }
  }
}

WebMCP Scripts

WebMCP is a mechanism for sites to expose tools, which are JavaScript functions with structured schema, that browser AI agents can call to interact with the site. AgentBoard polyfills and extends WebMCP, allowing you to author custom scripts that can be executed in context of the page. For those that remember: like Greasemonkey, but AI-controlled! Example script...

'use webmcp-tool v1';

export const metadata = {
  name: 'extract_prices',
  description:
    'Extract product prices from the current page. Returns price text and structured value for each element. Use for price comparison, deal finding, or cart analysis.',
  match: '*://example.com/*',
  inputSchema: {
    type: 'object',
    properties: {},
    additionalProperties: false,
  },
};

export async function execute() {
  const prices = Array.from(document.querySelectorAll('[class*="price"]')).map((el) => ({
    text: el.textContent.trim(),
    value: el.dataset.price || el.getAttribute('content'),
  }));

  return { prices, count: prices.length };
}

Save in Settings → My Tools. The AI can now call it when you ask about prices on example.com. See examples/ for more complete tool implementations.

Built-in WebMCP tools:

  • agentboard_read_page - Read page content as clean markdown with metadata (title, author, date)
  • agentboard_youtube_transcript - Video transcript extraction with timestamps (YouTube only)
  • agentboard_fetch_url - Fetch external URLs with optional markdown conversion

Commands

Fast interactions with expansion templates.

/explain how async/await works
→ "Explain $ARGUMENTS in simple terms with examples, use page context."

/tldr
→ "Summarize this page in 5 bullet points. Provide a short critique."

Development

pnpm install      # Install dependencies
pnpm run dev      # Start with hot reload
pnpm run build    # Production build
pnpm test         # Run tests
pnpm run check    # Type check + lint + test

Load dist/ folder in chrome://extensions (Developer Mode).


FAQ

What kind of MCP servers can I call?

Any MCP server that supports HTTP streaming. Add auth tokens if needed. Examples: internal APIs, databases, GitHub tools, company integrations. As long as the server speaks MCP over HTTP, it works. We do not support stdio MCP servers, but if you can host your stdio tools behind an streaming HTTP interface/proxy (e.g. via MCProxy or similar) then anything is possible.

What kind of scripts can I write with WebMCP?

Any JavaScript that interacts with the page. Extract data with CSS selectors. Click buttons. Submit forms. Modify content. Access page JavaScript state. Read cookies. Trigger events. Use URL match patterns to scope tools to specific sites. Full DOM access, full page context. If you can do it in the browser console, you can script it as a WebMCP tool.

How do site CSP policies and WebMCP interact?

Sites that deploy strict CSP (e.g. no dynamic scripts) may not allow custom tools to be executed — this is expected behavior. Built-in tools that ship with AgentBoard can execute in all context, but custom scripts are constrained by site's CSP policy.

What information does AgentBoard collect?

None. See PRIVACY.md.

README mirrored from the source repository 3 hours ago. The original is authoritative.

Questions

About Agentboard

How do I install Agentboard?

Run npx agentboard, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Agentboard safe to use with an AI agent?

Its trust score is 77 out of 100 (good). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Agentboard still maintained?

Yes — the latest release is v0.9.0 (7 Aug 2026), and the last commit was 6 months ago. The repository has 109 stars and 0 open issues.