Home/Compare/cc-switch vs mcpproxy-go

Comparison

cc-switch vs mcpproxy-go

Verdict

Pick cc-switch when cc-switch is primarily Rust; mcpproxy-go is Go; pick mcpproxy-go when mcpproxy-go is primarily Go; cc-switch is Rust.

Markdown twin · cc-switch alternatives · mcpproxy-go alternatives

GraphCanon updated today

cc-switch logo

cc-switch

farion1231/cc-switch

116kpushed Jul 11, 2026
vs
mcpproxy-go logo

mcpproxy-go

smart-mcp-proxy/mcpproxy-go

285pushed Jul 11, 2026

Trust & integrity

Signalcc-switchmcpproxy-go
Maintenance
Very active (0d since push)
As of today · github_public_v1
Very active (0d since push)
As of today · github_public_v1
Provenance
Not a fork · Personal account
As of today · github_public_v1
Not a fork · Organization account
As of today · github_public_v1
Security (OSV)
No MCP manifest
As of today · mcp_manifest
No criticals
As of today · osv@v1

Tagline

cc-switch
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
mcpproxy-go
Supercharge AI Agents, Safely

Stars

cc-switch
116k
mcpproxy-go
285

Forks

cc-switch
7.8k
mcpproxy-go
36

Open issues

cc-switch
1.9k
mcpproxy-go
14

Language

cc-switch
Rust
mcpproxy-go
Go

Adopt for

cc-switch
-
mcpproxy-go
-

Persona

cc-switch
-
mcpproxy-go
-

Runtime

cc-switch
-
mcpproxy-go
-

License

cc-switch
MIT
mcpproxy-go
MIT

Last pushed

cc-switch
Jul 11, 2026
mcpproxy-go
Jul 11, 2026

Categories

cc-switch
AI Agents, Developer Tools
mcpproxy-go
AI Agents, Developer Tools, LLM Frameworks

Trust and health

Open issues (now)

cc-switch
1.9k
mcpproxy-go
14

Owner type

cc-switch
User
mcpproxy-go
Organization

Security scan

cc-switch
No MCP manifest
mcpproxy-go
No criticals

Full report

cc-switch
Trust report
mcpproxy-go
Trust report

Choose cc-switch if…

  • cc-switch is primarily Rust; mcpproxy-go is Go.
  • Tags unique to cc-switch: ai-tools, claude-code, codex, desktop-app.
  • More GitHub stars (116k vs 285) - visibility, not fit.

When NOT to use cc-switch

  • AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
  • Developer Tools: A gateway is overkill when you're pinned to a single provider and model.

Choose mcpproxy-go if…

  • mcpproxy-go is primarily Go; cc-switch is Rust.
  • Tags unique to mcpproxy-go: ai, ai-agents, audit-logging, bm25.
  • Also covers LLM Frameworks.
  • mcpproxy-go ships Docker support for self-hosted deployment.

When NOT to use mcpproxy-go

  • AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
  • Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
  • LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

Explore

Sources

Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.

GitHub stars on cards: cc-switch 116k · mcpproxy-go 285 (synced Jul 11, 2026).

Common questions

What is the difference between cc-switch and mcpproxy-go?
cc-switch: A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io. mcpproxy-go: Supercharge AI Agents, Safely. See the comparison table for live GitHub stats and shared categories.
When should I choose cc-switch over mcpproxy-go?
Choose cc-switch over mcpproxy-go when cc-switch is primarily Rust; mcpproxy-go is Go; Tags unique to cc-switch: ai-tools, claude-code, codex, desktop-app; More GitHub stars (116k vs 285) - visibility, not fit.
When should I choose mcpproxy-go over cc-switch?
Choose mcpproxy-go over cc-switch when mcpproxy-go is primarily Go; cc-switch is Rust; Tags unique to mcpproxy-go: ai, ai-agents, audit-logging, bm25; Also covers LLM Frameworks; mcpproxy-go ships Docker support for self-hosted deployment.
When should I avoid cc-switch?
AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
When should I avoid mcpproxy-go?
AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Developer Tools: A gateway is overkill when you're pinned to a single provider and model. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
Is cc-switch or mcpproxy-go more popular on GitHub?
cc-switch has more GitHub stars (115,863 vs 285). Stars measure visibility, not whether either tool fits your constraints.
Are cc-switch and mcpproxy-go open source?
Yes - both are open-source projects on GitHub (cc-switch: MIT, mcpproxy-go: MIT).
Where can I find alternatives to cc-switch or mcpproxy-go?
GraphCanon lists graph-backed alternatives at cc-switch alternatives and mcpproxy-go alternatives (cc-switch markdown twin, mcpproxy-go markdown twin), ranked by typed relationship edges rather than popularity votes.
Is there a machine-readable version of this comparison?
Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
Which is better maintained, cc-switch or mcpproxy-go?
cc-switch: Very active. mcpproxy-go: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
Where are the full trust reports for cc-switch and mcpproxy-go?
GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: cc-switch trust report; mcpproxy-go trust report.