Cms vs Browser Gateway

In-depth architectural comparison of the Cms and Browser Gateway MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

C

Choose Cms when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Cms Details

Choose Browser Gateway when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Browser Gateway Details

Feature & Specification Comparison

Specification	C Cms Browser Automation	Browser Gateway Browser Automation
Summary	UXBERT Labs headless CMS: model, write and publish bilingual content, media, delivery checks.	AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.
Category & Scope	Browser Automation	Browser Automation
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "cms": {
      "command": "npx",
      "args": [
        "-y",
        "cms"
      ]
    }
  }
}

{
  "mcpServers": {
    "browser-gateway": {
      "command": "npx",
      "args": [
        "browser-gateway"
      ]
    }
  }
}

Related MCP Server Comparisons