What is the key difference between Charlotte and Cms?

Charlotte belongs to the Browser Automation category with local stdio execution, while Cms belongs to the Browser Automation category with cloud HTTP/SSE execution.

How do I install Charlotte or Cms in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Charlotte and Cms free or paid?

Charlotte operates under a Free / Open Source model (No auth required). Cms operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Charlotte lists 0 tools with 0 views and 0 GitHub stars. Cms lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Charlotte and Cms together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Charlotte or Cms in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Charlotte and Cms free to use, or do they require API keys?

Charlotte is listed under a Free / Open Source model with No auth required . Cms operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Charlotte and Cms at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both charlotte and cms as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Charlotte has a Quality Score of 28 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Cms holds a Quality Score of 45 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Charlotte vs Cms

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

At a Glance & Executive Verdict

Charlotte

Browser Automation · Local stdio

Quality: 28/100 (Emerging) | Auth: No auth required

Cms

Browser Automation · Remote HTTP/SSE

Quality: 45/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Charlotte if you need specialized Browser Automation tools running via a local process. Choose Cms if your workspace requires Browser Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

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).

Explore Charlotte Details

Choose Cms 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).

Explore Cms Details

Feature & Specification Comparison

Specification	C Charlotte Browser Automation	C Cms Browser Automation
Summary	Renders web pages into structured, agent-readable representations using headless Chromium.	UXBERT Labs headless CMS: model, write and publish bilingual content, media, delivery checks.
Category & Scope	Browser Automation	Browser Automation
Quality signal

Tools & Capabilities Breakdown

Charlotte Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Cms Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Charlotte Configuration

mcpServers (Claude Desktop / Cursor)

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

Cms Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cms": {
      "url": "https://cms.uxbert.ai"
    }
  }
}

Frequently Asked Questions

Charlotte is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Cms belongs to Browser Automation using remote streaming HTTP/SSE transport. Select Charlotte when you need capabilities focused on browser automation and Cms when you require tools for browser automation.

More alternatives to Charlotte More alternatives to Cms Browser Automation category hub