BrowserPair

com.browserpairPublished by browserpair.comOfficial publisherv1.0.0Updated Oct 24, 2026

Connect AI agents to your own Chrome with scoped access, approvals, and verified task results.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

Remote MCP server that connects AI agents to your own Chrome browser with scoped access, approvals, and verified task results.

What you can do
  • Connect an AI agent to your own Chrome browser session.
  • Limit what the agent can reach through scoped access.
  • Require approvals before actions are carried out.
  • Return verified results for completed tasks.
  • No individual tools are documented, so the exact operations are not listed.
When to use it
Use it when you want an assistant to work inside your own logged-in Chrome browser rather than a separate headless one, and you want access limits and approval steps around what it does.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or environment variables are declared. Sign-in is required via OAuth.
Before you install
The agent operates your personal Chrome session, so it may reach sites and accounts you are signed into; rely on the scoped access and approval controls before granting it. Sign-in is through OAuth, so review which permissions you authorize. The published listing does not document the individual tools or their side effects.

Installation

In SourceWeft

  1. Open BrowserPair in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.browserpair%2Fbrowserpair/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "browserpair": {
      "type": "http",
      "url": "https://mcp.browserpair.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 24, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.