MCP Relay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELAY_MCP_TOKEN | Yes | A token used by the AI agent to connect to the Relay Server's MCP endpoint. Must be 32–256 printable ASCII characters without spaces. | |
| RELAY_CLIENT_TOKEN | Yes | A token shared between the Relay Server and Relay Client. Must be 32–256 printable ASCII characters without spaces. | |
| RELAY_SERVER_MCP_HOST | No | Bind address for the MCP listener. | 127.0.0.1 |
| RELAY_SERVER_MCP_PORT | No | Port for the MCP listener. | 8000 |
| RELAY_SERVER_CLIENT_HOST | No | Bind address for the Client listener. | 127.0.0.1 |
| RELAY_SERVER_CLIENT_PORT | No | Port for the Client listener. | 8001 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| relay_statusA | Report the Relay Server, the connected Client and its MCP servers. Call it first to check that the Client is connected and which server
aliases run, when a tool is missing or fails, and after an
administration change. Read-only. Client details come from a short
live probe; when the Client is busy or unreachable the last good
answer is returned as |
| relay_registry_searchA | Search the official MCP Registry for servers to add (read-only, server-side). Use it to discover a server that is not configured yet; for the
servers the Client already runs, use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.