Developer · Local MCP server
Weboperator
Hands your live Chrome tab to any MCP client - snapshot, navigate, click, type, extract.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.KazKozDev/weboperator- Version
- 1.5.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-01
- Updated
- 2026-09-01
- Publisher
- KazKozDev (GitHub) · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/KazKozDev) · how
- Repository
- github.com/KazKozDev/WebOperator
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | weboperator-mcp | 1.5.1 | stdio |
How to connect Weboperator
Weboperator runs locally from a Node.js package published to the npm registry: weboperator-mcp version 1.5.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y weboperator-mcp@1.5.1. It reads these environment variables: WEBOPERATOR_BRIDGE_PORT, WEBOPERATOR_AGENT_SOCKET and WEBOPERATOR_API_TOKEN (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"weboperator": {
"command": "npx",
"args": [
"-y",
"weboperator-mcp@1.5.1"
],
"env": {
"WEBOPERATOR_BRIDGE_PORT": "<value>",
"WEBOPERATOR_AGENT_SOCKET": "<value>",
"WEBOPERATOR_API_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from KazKozDev (GitHub)
| Server | Runs |
|---|---|
| AbscissaSafety-aware MCP server for Linear issues, projects, cycles, and dependencies. | Local · stdio |
| footnote-mcpSource-grounded web research: search, extraction, verification, and browser automation. | Local · stdio |
| MCP Search ServerWeb search, content extraction, PDF parsing, plus datetime and geolocation tools. No API keys. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Webhook.site MCP ServerCapture HTTP, email, and DNS callbacks with webhook.site from MCP clients. | Local · stdio |
| WebhookTest.netAnonymous webhook capture, inspection, waiting, and response configuration for AI agents. | Remote · HTTPLive check: ✓ handshake |
| Webmcpactionreceipt MCPPaid remote MCP for WebMCP action receipt MCP, structured receipts, audit logs, and reviewer-ready e. | Remote · HTTPLive check: ✗ no handshake |
| WebnavA zero-LLM MCP server that replays recorded site maps instead of re-exploring browser routes. | Local · stdio |
| WebsharpSearch the web and extract article text for LLMs. | Local · HTTP |
| Website Change Monitor & Deterministic DiffDeterministic webpage change detection, hashes and text diffs for recurring monitoring via x402 MCP. | Remote · HTTPLive check: ✓ handshake |
| Website SearchImprove security writing, score it against rubrics, plan IR, CTI, vuln, and product strategy. | Remote · HTTPLive check: ✓ handshake |
| Website StarterCreate Markdown instructions for AI agents to build, deploy, and maintain an Astro website. | Remote · HTTPLive check: ✓ handshake |