| title | MCP Server Integration |
|---|
Vibium ships an MCP (Model Context Protocol) server so AI agents can drive the browser as a first-class tool, alongside their other tools.
When Vibium is registered as an MCP server, the agent gains tools that map 1:1 to the CLI commands: navigation, mapping, finding, clicking, filling, capture, and so on. The agent can use them directly without spawning shell subprocesses.
claude mcp add vibium -- npx -y vibium mcpgemini mcp add vibium npx -y vibium mcpAny client that can spawn an MCP server over stdio can use Vibium. The command to spawn is:
npx -y vibium mcpor, if you have already installed Vibium globally:
vibium mcpThe MCP server runs locally as a subprocess of your client. It manages the same browser daemon the CLI uses, so:
- CLI commands and MCP-driven commands share state.
- A screenshot or recording started from one interface is visible to the other.
- Stopping the server stops the client end, not the browser daemon.
Inside an agent, the tools generally appear with names matching the CLI
verbs (go, map, find, click, fill, screenshot, text, …). The
agent's tool-use loop is:
- Call
gowith a URL. - Call
map(orfind) to discover references. - Call
click/fill/selectto interact. - Call
text/screenshotto read the result.
This is the same loop documented in Getting Started; MCP just removes the shell from the middle.
If the agent reports that the tool isn't registered, confirm with your
client's mcp list (or equivalent) command, then try re-registering. If the
server fails to start, run vibium mcp directly to surface any error
messages, and check that the bundled browser has been downloaded by running
a quick vibium go https://example.com first.