Arc Relay

Arc Relay is a management proxy for Model Context Protocol (MCP) servers.

  • AI
  • Development
  • Tools & Utilities
Arc Relay is a management proxy for Model Context Protocol (MCP) servers. It sits between your AI tools (Claude Code, Claude Desktop, Cursor, etc.) and your MCP servers, providing a single authenticated endpoint that handles Docker container lifecycle, health monitoring, OAuth flows, access control, and multi-transport proxying. Manage all your MCP servers from one web UI. (Formerly MCP Wrangler)

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
86last commit 25 days ago
Popular
3449 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
1012 GB minimum RAM
Security check
94no serious findings, 1 minor, CI, tests

Availability: platform listings confirmed today, links checked 24 days ago

GitHub stars
49
Open issues
11
Last commit
2026-10-27
Latest release
v0.1.6
License
MIT
Activity
rising

Checked 8 days ago - source: GitHub (comma-compliance/arc-relay)

Resources & Compatibility

Minimum requirements: 12 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set ApplicationUrl to the right address ApplicationUrl is the address the app tells other programs to use, and the example uses http://localhost:5000/. If you run it on another host or port but leave this old, other programs may call the wrong place and your API calls won't arrive. source
  • Test a printed URL after startup The starter example prints URLs such as /api/my-app/get-greeting and /.cratis/me when it starts. Opening one in a browser is a quick check that the app is running and reachable, so you can spot a wrong address or stopped app early. source
  • Optional: publish an API help page The OpenAPI example can publish an API description at /api/openapi.json, which lists the endpoints for people using your API. This is optional and does not make the app work, but it can help with testing and documentation. source
  • Unified MCP endpoint Configure MCP-capable AI tools to use Arc Relay's single endpoint, /mcp/{server-name}, to reach each managed MCP server. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can Arc Relay be used as a self-hosted MCP proxy without connecting to an external service?

Yes. It works standalone as a self-hosted MCP control plane, and connection to Comma Compliance Arc is optional for managed compliance policies, audit trails, and enterprise reporting.

Is there a web interface for managing MCP servers?

Yes. It provides a web UI for managing all of your MCP servers.

Does Arc Relay handle OAuth and access control for MCP traffic?

Yes. It handles OAuth flows, access control, and multi-transport proxying for MCP servers.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads