What is the key difference between Paraíso and Campo Belo?

Paraíso belongs to the Developer Tools category with local stdio execution, while Campo Belo belongs to the Developer Tools category with local stdio execution.

How do I install Paraíso or Campo Belo 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 Paraíso and Campo Belo free or paid?

Paraíso operates under a Free / Open Source model (No auth required). Campo Belo operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Paraíso lists 0 tools with 0 views and 0 GitHub stars. Campo Belo lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Paraíso and Campo Belo 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.

Side-by-Side Model Context Protocol Comparison

Paraíso vs Campo Belo

In-depth architectural comparison of the Paraíso and Campo Belo 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

Paraíso

Developer Tools · Local stdio

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

Campo Belo

Developer Tools · Local stdio

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

Verdict Summary: Choose Paraíso if you need specialized Developer Tools tools running via a local process. Choose Campo Belo if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Paraíso when:

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

Explore Paraíso Details

Choose Campo Belo when:

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

Explore Campo Belo Details

Feature & Specification Comparison

Specification	P Paraíso Developer Tools	C Campo Belo Developer Tools
Summary	Paraíso — neighborhood directory: local places, events, menus, offers, and services.	Campo Belo — neighborhood directory: local places, events, menus, offers, and services.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Paraíso Tools (0)

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

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

Paraíso Configuration

mcpServers (Claude Desktop / Cursor)

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

Campo Belo Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Paraíso is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Campo Belo belongs to Developer Tools using local stdio subprocess. Select Paraíso when you need capabilities focused on developer tools and Campo Belo when you require tools for developer tools.

More alternatives to Paraíso More alternatives to Campo Belo Developer Tools category hub Canonical compare URL