What is the key difference between Mcpproxy Go and Toolport?

Mcpproxy Go belongs to the Aggregators category with local stdio execution, while Toolport belongs to the Aggregators category with local stdio execution.

How do I install Mcpproxy Go or Toolport 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 Mcpproxy Go and Toolport free or paid?

Mcpproxy Go operates under a Free / Open Source model (No auth required). Toolport operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mcpproxy Go lists 6 tools with 6 views and 373 GitHub stars. Toolport lists 6 tools with 4 views and 214 GitHub stars.

Can I use both Mcpproxy Go and Toolport 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

Mcpproxy Go vs Toolport

In-depth architectural comparison of the Mcpproxy Go and Toolport 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

Mcpproxy Go

Aggregators · Local stdio

Quality: 51/100 (Good) | Auth: No auth required

Toolport

Aggregators · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Verdict Summary: Choose Mcpproxy Go if you need specialized Aggregators tools running via a local process. Choose Toolport if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mcpproxy Go when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: BM25-based tool filtering, Single HTTP endpoint for multiple MCP servers, Server quarantine and manual approval.

Explore Mcpproxy Go Details

Choose Toolport when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local MCP gateway, Cross-client server profiles, OS keychain credential storage.

Explore Toolport Details

Feature & Specification Comparison

Specification	Mcpproxy Go smart-mcp-proxy Aggregators	Toolport tsouth89 Aggregators
Summary	Local MCP proxy with BM25 tool filtering, quarantine security, activity logging, and web UI. Routes multiple servers through a single endpoint.	One local gateway and manager for all your MCP servers, shared across every AI coding tool (Claude, Cursor, VS Code, Codex, and more). Set up and authenticate each server once; lazy discovery keeps each agent's context small, and keys stay in your OS keychain. No Docker, no cloud.
Category & Scope

Tools & Capabilities Breakdown

Mcpproxy Go Tools (6)

BM25-based tool filtering

Single HTTP endpoint for multiple MCP servers

Server quarantine and manual approval

Activity logging and web UI

Optional Docker-based security scanners

Cross-platform core binary

Toolport Tools (6)

Local MCP gateway

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

Mcpproxy Go Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "smart-mcp-proxy-mcpproxy-go": {
      "command": "npx",
      "args": [
        "-y",
        "smart-mcp-proxy-mcpproxy-go"
      ]
    }
  }
}

Toolport Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Mcpproxy Go is categorized under Aggregators and uses a local stdio subprocess. In contrast, Toolport belongs to Aggregators using local stdio subprocess. Select Mcpproxy Go when you need capabilities focused on aggregators and Toolport when you require tools for aggregators.

More alternatives to Mcpproxy Go More alternatives to Toolport Aggregators category hub