code-relay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bind_projectC | Bind the current project and branch to Code Relay. |
| create_checkpoint_inviteC | Create a short-lived checkpoint join link. |
| join_checkpointC | Join a branch-scoped checkpoint subscription. |
| watcher_statusC | Show the legacy local watcher state. |
| stop_watcherC | Stop the legacy local watcher state. |
| doctorC | Run non-mutating local health checks. |
| publish_runbookB | Validate and publish a runbook.md. |
| statusC | Show runbook and receipt status. |
| fetch_receiptC | Load and validate a runbook receipt. |
| analyzeC | Analyze a runbook receipt and determine the next state. |
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 10 tools
Most tools target distinct actions and resources, such as bind_project, publish_runbook, and fetch_receipt. The main ambiguity is between status and watcher_status, though their descriptions clarify that one covers runbook/receipt status and the other legacy watcher state.
Most tools follow a verb_noun pattern like create_checkpoint_invite and publish_runbook. However, doctor and status are bare nouns, and analyze is a bare verb, creating a mixed convention that is readable but not consistently patterned.
With 10 tools, the server is well-scoped for its domain. Each tool appears to cover a meaningful part of the project binding, checkpoint, and runbook workflow without unnecessary bloat.
The runbook and receipt workflow is well covered with publish, status, fetch, and analyze. However, lifecycle gaps exist: there is no unbind_project, no checkpoint leave/revoke tool, and no way to start the legacy watcher, only to stop it.