MCP Monkey (Chrome Browser)
Bridges AI coding agents to Chrome browser functionality through a WebSocket connection between an MCP server and Chrome extension. Users define custom JavaScript functions that run inside authenticated browser sessions, exposed as callable MCP tools. The server communicates via stdio with the agent and via WebSocket with the extension, which executes scripts in the page's MAIN world with full DOM and cookie access. Supports dynamic script registration through the extension popup, automatic tab matching by URL pattern, and async execution with 30-second timeouts.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- browser-automation
- Source
- PulseMCP
- Repository
- github.com/krngd2/mcp-monkey
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve MCP Monkey (Chrome Browser) from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.