Skip to main content
Any AI tool that speaks MCP over HTTP can use BrowserOS neo. Adding the MCP server connects the two, and installing the BrowserOS neo skill on top improves the experience. The MCP syntax varies by tool, and so does the way skills are loaded. Here are the tools we have documented so far. First, grab the endpoint URL from BrowserOS neo. Open a new tab, click MCP in the sidebar, and click Copy at the top of the page. It looks like this:
Now pick your AI tool below.
The examples name the server browseros-neo, matching the one-click setup. The name is yours to choose, but whatever you pick is the name your AI tool will know the browser by.

Install the skill

The skill is one SKILL.md file, published from the BrowserOS repository. Most agents read skills from a shared .agents/skills directory, and the quickest way to put it there is the skills.sh CLI:
Keep the --skill browseros-neo flag. Without it the command installs every skill published from that repository, including several we use to work on BrowserOS itself, which have no business in your agent.
That writes ./.agents/skills/browseros-neo/SKILL.md in the current project and symlinks it for agents that use their own directory. Add -g instead to install it once for every project. Not every agent reads .agents/skills, so check your tool below.

Hermes Agent

Hermes Agent from Nous Research supports connecting to external HTTP MCP servers via its YAML config. Full details in Hermes’ MCP docs. Open ~/.hermes/config.yaml and add a mcp_servers entry:
Then reload Hermes:
  • Inside an existing hermes chat session, run /reload-mcp.
  • Or restart Hermes.
Hermes also has a CLI command that adds a server interactively: hermes mcp add browseros-neo. Either path works. Adding the skill. Hermes does not read .agents/skills. It keeps skills in ~/.hermes/skills/, so install it from the file directly:
Check it landed with hermes skills list, or /skills inside a chat session. Hermes loads the name and description up front and pulls the full text only when it needs it, so the skill costs almost nothing until it is used. Full details in Hermes’ skills docs.

Vercel AI SDK

The Vercel AI SDK supports MCP tools via the @ai-sdk/mcp package. Full details in the AI SDK MCP docs. Point the client at BrowserOS neo’s endpoint URL, pull the tools, and pass them into streamText or generateText.
The AI SDK docs recommend closing the client once you’re done. In streaming code that means mcpClient.close() inside onFinish. In non-streaming code, use a try / finally block. Adding the skill. The AI SDK is a library rather than an agent, so nothing discovers skills for you. Run the npx skills add command above, then read the file into your system prompt:
For more than one skill, the AI SDK’s agent skills guide covers loading names and descriptions up front and fetching the full text on demand with a loadSkill tool.

OpenClaw

OpenClaw is an open-source personal AI assistant that can act as an MCP client. Full details in OpenClaw’s MCP docs. The fastest path is the CLI:
Or edit ~/.openclaw/openclaw.json directly:
Verify the connection with the built-in doctor:
Adding the skill. OpenClaw already reads .agents/skills, both in the workspace and at ~/.agents/skills, so the npx skills add command above is enough and there is nothing else to wire up. If you would rather use OpenClaw’s own installer, it takes a skills.sh reference:
Add --global to install it for every workspace. Confirm with openclaw skills list. Full details in OpenClaw’s skills docs.

Any other MCP-compatible AI tool

The pattern is the same: paste http://127.0.0.1:9200/mcp into the AI tool’s own MCP server config, using whatever syntax that tool expects. BrowserOS neo’s endpoint uses Streamable HTTP transport (per the current MCP spec), so any client that supports Streamable HTTP works. For the skill, run npx skills add browseros-ai/browseros --skill browseros-neo and then check where your agent looks for skills. Most read .agents/skills and will find it with no further work. If yours keeps them somewhere of its own, copy .agents/skills/browseros-neo/SKILL.md into that directory, or point its own installer at the file:
If you get your AI tool talking to BrowserOS neo and want to help others do the same, please open a discussion with the setup steps.

Where to next

How BrowserOS neo works

A guided walkthrough from install to your first AI-driven session.

One-click setup

The AI tools we support with one click today.