Skip to main content
AI apps that speak MCP with OAuth can connect to BrowserPair without a copied agent key. The app sends you to BrowserPair, you sign in and choose its limits, and the app receives a short-lived token that works only on Remote MCP.

Your account

Sign in with the same BrowserPair account that owns your connected browser.

Your limits

Pick one browser, the websites, what the app may do and when it must ask you.

Your off switch

Disconnect under Agent access → Connected apps; access ends immediately.

Connect

1

Connect a browser first

Install the BrowserPair extension and pair the Chrome profile you want the app to use. See Quickstart.
2

Add BrowserPair in your AI app

Use the server URL https://mcp.browserpair.com and choose OAuth if the app asks. See ChatGPT for the ChatGPT steps.
3

Choose the app's limits

BrowserPair shows the app’s name, whether its identity is published by its own domain, and the address it returns to. Choose the browser, at least one website, what it may do and the approval preset, then select Allow.
4

Ask for a browser task

The app can now list your browser, start tasks inside those limits, and report verified results.

What a connected app can and cannot do

Website content is untrusted data. Nothing a page or the app’s model says can widen these limits.

Approvals and uncertain results

  • When a step needs your decision, the task pauses and the app is told to ask you to approve or deny it in the BrowserPair card in Chrome.
  • If BrowserPair cannot confirm whether an action took effect, it never repeats it automatically. The app is told to look at the page again before deciding.
  • Each result says whether the outcome was verified on the page or needs your review.

Manage connected apps

Open Agent access in the BrowserPair App. Each connected app shows its browser, websites, permissions and when it was last used. Disconnect ends its tokens at once and stops its running tasks. Removing the only browser an app may use also disconnects it. Connected apps count toward your plan’s agent limit, like agent keys.

For MCP client developers

Authorization responses include iss (RFC 9207). Unauthenticated MCP requests receive 401 with WWW-Authenticate: Bearer resource_metadata="…". Reusing a rotated refresh token revokes the connection. Product history: Changelog.