MCP Server
Vibium ships an MCP (Model Context Protocol) server. Register it with an AI client and the agent can drive a real browser through tool calls, next to its other tools.
npx -y vibium mcpThat command is the whole server: JSON-RPC over stdio, no hosted service, no account. Client Setup has the exact steps for Claude Code, Claude Desktop, Gemini CLI, and any other MCP client.
What the agent gets
Section titled “What the agent gets”The tools mirror the CLI commands, so everything in the Command Reference has a tool-call form.
| Tools | What they do |
|---|---|
browser_start, browser_stop | Start and stop the browser session |
browser_navigate, browser_back, browser_reload | Move between pages |
browser_map, browser_find, browser_find_all | Discover elements and get @e1-style references |
browser_click, browser_fill, browser_type, browser_select, browser_keys | Act on elements |
browser_get_text, browser_get_html, browser_a11y_tree, browser_screenshot | Read the result |
browser_new_page, browser_list_pages, browser_switch_page | Work with several tabs |
vibium_run, vibium_check | Hand over a whole goal, or verify a claim |
The Tool Reference lists every tool with its parameters.
The tool-use loop
Section titled “The tool-use loop”- Call
browser_navigatewith a URL. - Call
browser_map(orbrowser_find) to discover references. - Call
browser_click/browser_fill/browser_selectto interact. - Call
browser_get_text/browser_screenshotto read the result.
A tool call names the tool and passes JSON arguments:
{ "name": "browser_navigate", "arguments": { "url": "https://example.com" } }This is the same loop as the CLI; MCP removes the shell from the middle.
Run and Check
Section titled “Run and Check”vibium_run drives the browser toward a goal. vibium_check independently
verifies a claim and returns a verdict with evidence. Both use the AI
settings in the server’s environment and take optional per-call
provider/model overrides; see Model providers.
What runs where
Section titled “What runs where”The MCP server runs locally as a subprocess of your client. It manages the same browser daemon the CLI uses, so:
- CLI commands and MCP tool calls 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.
Screenshots taken through MCP are saved to ~/Pictures/Vibium/
(Pictures\Vibium\ on Windows). Change that with --screenshot-dir; see
Client Setup.