pulsemcp Safe content atomic mcp-remote

Chrome Browser Control

Chrome MCP Server provides fine-grained control over a Chrome browser instance through the Chrome DevTools Protocol (CDP). It enables AI assistants to navigate web pages, interact with elements, type text, and extract page content through a set of specialized tools. The server implements SSE transport for the Model Context Protocol and includes features like automatic handling of dynamic content, mutation tracking, and prevention of new window/tab openings. Particularly valuable for workflows requiring web automation, form filling, or content extraction directly within conversation interfaces.

Cognium trust score

50%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

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/lxe/chrome-mcp
Author type: human
Updated: 2026-04-27

View source Find related skills

MCP

Resolve Chrome Browser Control 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

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"