mcp-proxy
★ 2.8k
vs
gitlab-mcp
★ 2.1k
mcp-proxy vs gitlab-mcp
mcp-proxy: mcp-proxy is a versatile tool designed to switch between various server transport protocols, primarily facilitating communication between stdio and SSE/Streamable HTTP. It operates in two main modes: proxying stdio to a remote SSE server, or exposing a local stdio server via an SSE endpoint.; gitlab-mcp: A community MCP server for GitLab with 276 tools across projects, merge requests, issues, pipelines, wikis and releases, loaded in toolsets that can be activated at runtime. It supports PAT and OAuth auth, read-only mode, self-hosted instances and three transports.
01
TL;DR
mcp-proxyMCP Servers · ★ 2.8k
When to choose:
- Your client only speaks stdio (such as Claude Desktop) and the MCP server you need is remote over SSE or Streamable HTTP.
- You want to expose a local stdio server over SSE or Streamable HTTP so remote clients can reach it.
- You want a small single-purpose tool that can host several named stdio servers from an mcpServers-style JSON file.
When to skip:
- You need authentication, tool filtering or an admin UI: the README is about transport, not access control.
- Your client already supports remote transports natively, so a proxy adds a process for no gain.
- You need clear licence terms: our data shows no licence for the repository, so confirm them first.
gitlab-mcpMCP Servers · ★ 2.1k
Let a coding agent review and comment on merge requests
02
Side-by-Side Comparison
03
Features
mcp-proxy01Proxy stdio clients to remote SSE/Streamable HTTP servers.
02Expose local stdio servers as remote SSE endpoints.
03Manage multiple stdio-based MCP servers via named server configurations.
04Integrated OAuth2 authentication for client connections.
05Configurable transport types, headers, host/port, and CORS settings.
gitlab-mcp01276 tools grouped in toolsets, plus discover_tools and execute_graphql
02Two-step merge request review: list changed files, then batched diffs
03Personal access token, OAuth2 browser flow and remote per-request auth
04stdio, SSE and Streamable HTTP transports; works with self-hosted GitLab
05Optional JMESPath filtering to shrink tool results
04
Use Cases
mcp-proxy↳Enable stdio-only clients (e.g., Claude Desktop) to connect to remote SSE/Streamable HTTP servers.
↳Allow remote LLM clients to access local stdio-based MCP servers via an SSE interface.
↳Consolidate and manage multiple distinct stdio MCP servers via named proxy endpoints under a single instance.
gitlab-mcp↳Let a coding agent review and comment on merge requests
↳Check pipeline status and job logs from Claude Code or Cursor
↳Manage issues, milestones and wikis on a self-hosted GitLab
05
Best For
mcp-proxyEssentialTrending
gitlab-mcpTrending
FAQ
FAQ
What is the difference between mcp-proxy and gitlab-mcp?
Both mcp-proxy and gitlab-mcp are in the MCP Servers category. mcp-proxy has 2.8k stars, while gitlab-mcp has 2.1k stars.
Which is better, mcp-proxy or gitlab-mcp?
The best choice depends on your use case. Choose mcp-proxy if Enable stdio-only clients (e.g., Claude Desktop) to connect to remote SSE/Streamable HTTP servers., and gitlab-mcp if Let a coding agent review and comment on merge requests.
Is mcp-proxy free or open source?
Yes, mcp-proxy is open source on GitHub (MIT).
Is gitlab-mcp free or open source?
Yes, gitlab-mcp is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→