Requirements
- An MCP client such as Claude Desktop, Cursor, Codex, or your own MCP runner
- For hosted Browser MCP: a StableBrowse API key from the settings page
- For local Browser MCP: Node.js 20 or newer and a StableBrowse MCP checkout
Hosted Browser MCP
Hosted Browser MCP is the recommended setup for end users. The browser runs in StableBrowse cloud; your LLM app only needs the MCP endpoint and your StableBrowse API key.- Sign in to StableBrowse.
- Open settings.
- Create an API key.
- Add the hosted Browser MCP endpoint to your MCP client:
- Send the API key as a bearer token.
Your LLM key stays with your LLM app or model provider. The StableBrowse API key authenticates access to the hosted browser.
Local install
Hosted Browser MCP does not require a local browser process. If you want to run the MCP server yourself, use a source checkout:Run over stdio
Most desktop MCP clients use stdio:Run as an HTTP endpoint
For local integration tests:
For a hosted deployment that accepts dashboard-created StableBrowse API keys:
Common options
Environment variables use the
STABLEBROWSE_* prefix. For example:
First successful run
In a typical run the agent should:- call
create_session - call
navigate - call
content.get_markdown,extract.page_summary, orsnapshot - use
click,fill,fill_form, orinteractif action is needed - return the final answer
