A
licenseNot graded
qualityC
maintenanceExposes local stdio MCP servers to chat AIs through temporary public URLs, providing both a Streamable HTTP gateway and a REST+OpenAPI bridge for integration with ChatGPT and other clients.
MIT
MCP Relay
by kxlion
Related Servers
Alternatives to MCP Relay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables running local MCP servers on machines behind NAT and accessing their tools from anywhere through a single Streamable HTTP endpoint, without opening any inbound ports.MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI-driven interactions with Minecraft through a WebSocket-based server and MCP protocol, allowing external MCP clients and in-game chat to trigger AI tools.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables cloud AI agents to access local STDIO MCP servers and their tools through a single authenticated Streamable HTTP endpoint, optionally tunneled via ngrok.MIT
- AlicenseNot gradedqualityDmaintenanceEnables browsers to act as MCP servers by relaying tools, resources, and prompts to AI agents via a WebSocket-to-stdio bridge.7 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to securely connect to a paired Windows machine through a self-hosted Cloudflare relay and use its local filesystem and command-execution tools over Streamable HTTP and WebSocket.92 npm1MIT
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation4/5
relay_status (report configured Client/servers) and relay_registry_search (discover unconfigured servers) have clearly distinct purposes, and each description explicitly redirects to the other for the complementary case. Only minor overlap in that both are read-only discovery/observability operations, but boundaries are unambiguous.
Naming Consistency4/5
Both tools use a consistent snake_case 'relay_' prefix, forming a predictable namespace. The suffix pattern is not strictly verb_noun (status vs registry_search), a minor deviation, but naming is coherent and readable.
Tool Count2/5
Only two tools for a server whose purpose (relaying/managing an MCP Client and its servers) implies administrative capability; the surface feels notably thin. Descriptions even reference actions like 'administration change' that no tool exposes.
Completeness2/5
A clear dead end exists: relay_registry_search returns a 'name' described as 'the source for adding that server,' yet there is no tool to add, remove, or invoke anything. Status and discovery are covered, but the core lifecycle implied by the domain is missing.
Maintenance
ActivityMaintained
ResponsivenessNo issues