OpenBrowse

MCP documentation server

Use the openbrowse.co MCP endpoint to search OpenBrowse documentation and the published OpenAPI contract; it cannot operate a browser-agent instance.

https://openbrowse.co/mcp is a documentation-only Model Context Protocol server for this website. It helps an MCP client find and read the public OpenBrowse documentation and the published OpenAPI description without scraping the site manually. It is useful when an assistant needs an answer about installation, the self-hosted v3 API, authentication, profiles or error handling.

What it can do

The server exposes documentation knowledge only. Its tools search the OpenBrowse docs and OpenAPI material that this website publishes, then return the relevant source. It does not hold an OpenBrowse API key, a dashboard login, a browser profile, or access to any visitor’s infrastructure.

What it cannot do

The MCP server cannot create sessions, run browser tasks, retrieve results from your machine, manage profiles, call a model provider, receive webhooks or control an OpenBrowse instance in any way. There is no managed OpenBrowse browser API at openbrowse.co.

To automate a browser, install OpenBrowse on infrastructure you control and call that instance’s /v3 REST API with its own bearer token. The v3 API reference is the integration contract for the runtime; authentication explains how to secure it.

Choosing the right endpoint

Use /mcp when an MCP client needs project documentation. Use https://your-host/v3 when your own application needs to create or inspect browser-agent sessions. They are deliberately separate: one is public read-only documentation, and the other is the authenticated API of a self-hosted runtime.

On this page