What is the key difference between Campo Belo and Pinheiros?

Campo Belo belongs to the Developer Tools category with local stdio execution, while Pinheiros belongs to the Developer Tools category with local stdio execution.

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

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

Which MCP server has more tools and community activity?

Campo Belo lists 0 tools with 0 views and 0 GitHub stars. Pinheiros lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Campo Belo and Pinheiros 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

Campo Belo vs Pinheiros

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

Campo Belo

Developer Tools · Local stdio

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

Pinheiros

Developer Tools · Local stdio

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

Verdict Summary: Choose Campo Belo if you need specialized Developer Tools tools running via a local process. Choose Pinheiros 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 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

Choose Pinheiros 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 Pinheiros Details

Feature & Specification Comparison

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

Tools & Capabilities Breakdown

Campo Belo Tools (0)

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

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

Campo Belo Configuration

mcpServers (Claude Desktop / Cursor)

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

Pinheiros Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Campo Belo More alternatives to Pinheiros Developer Tools category hub