Charlotte vs Scout

In-depth architectural comparison of the Charlotte and Scout 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?

Choose Charlotte 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).
• Primary tools included: Structured, token-efficient page representations, Persistent headless Chromium sessions, Semantic, spatial, and CSS-selector element search.

Explore Charlotte Details

Choose Scout when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Embedded MCP server in a static Go binary, Direct Chrome DevTools Protocol browser control, DOM diffing and token-aware observation.

Explore Scout Details

Feature & Specification Comparison

Specification	Charlotte Browser Automation	Scout Browser Automation
Summary	Renders web pages into structured, agent-readable representations using headless Chromium.	Browser automation MCP server with 84 tools. Pure CDP, DOM diffing, vision hybrid.
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": {
    "charlotte": {
      "command": "npx",
      "args": [
        "@ticktockbent/charlotte"
      ]
    }
  }
}

{
  "mcpServers": {
    "scout-2": {
      "url": "https://api.groq.com/openai"
    }
  }
}

Related MCP Server Comparisons