Agent MCP Directory

Browser Use: MCP server, CLI and agent surfaces

Yes: Browser Use runs a public MCP server at api.browser-use.com that listed 7 tools to a client with no credentials on 4 November 2026. Examples: run_session, send_task, get_session. It speaks streamable-http, protocol 2024-11-05. Ora's cached score for browser-use.com is 91, grade A, read on 5 November 2026.

Fact sheet

CompanyBrowser Use (registry title: browser-use.com)
Domainbrowser-use.com
CategoryAgent Tools (Ora leaderboard category)
MCP serverVerified (No authentication)
Ora score91, grade A; Ora scanned the domain on 2 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for browser-use.com, a vendor-published score)
Company found throughOra's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://api.browser-use.com/v3/mcp
How it was foundlisted in Ora's public leaderboard
Transportstreamable-http
HTTP status200
Protocol version2024-11-05
Serverbrowser-use-v3-agent 3.0.0
Capabilitiestools
Tools7
Resources0
Prompts0
Connected4 November 2026, 20:02 UTC
Handshake time1,437 ms over 1 attempt

Tools listed

7 tools

  • run_session
  • send_task
  • get_session
  • get_session_messages
  • stop_session
  • list_sessions
  • list_browser_profiles

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:56:45Z https://api.browser-use.com/v3/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1589 ms
  • 20:02:17Z https://api.browser-use.com/v3/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1437 ms

Authentication

Auth typeNo authentication

The sign-in route, step by step

  1. Send the handshake to https://api.browser-use.com/v3/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Browser Use. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileFound: docs.browser-use.com (JSON, via a direct request).
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataFound: browser-use.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.browser-use/browser-use
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.