Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLAUDE_PROJECT_DIRNoProject directory used to match autostart.projects entries; defaults to the current directory.
MCP_PATCHBAY_DEBUGNoSet to 1 to copy every child's redacted stderr into the patchbay's own stderr log.
MCP_PATCHBAY_CONFIGNoPath to the patchbay config file. Overridden by --config; defaults to ~/.config/mcp-patchbay/servers.json.
MCP_PATCHBAY_MCP_REMOTE_BINNoReplaces the mcp-remote script used for remote servers. Intended for tests; normally unset.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

mcp-patchbay hosts the MCP servers listed below and can switch them on and off during the session. Call servers for their current state, enable {name} to turn one on (its tools then appear as __; some servers need a person to approve), and disable {name} to turn it off again. info {name} shows a server's own instructions. Servers:

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
serversA

Lists every MCP server the patchbay can host: name, description, policy (allow, confirm, deny), state (off, starting, on, failed, waiting-for-sign-in), tool count when on, and which ones can be enabled.

enableA

Starts a hosted MCP server and adds its tools, named __. Servers with policy confirm ask a person first; deny servers cannot be enabled. Returns the tool count, sample tool names and the server's instructions.

disableA

Stops a hosted MCP server and removes its tools. Refused while it still has calls in flight.

restartB

Stops and starts a hosted MCP server. No new confirmation if it is already on; otherwise behaves like enable.

infoA

Shows a hosted server's description, policy, state, recent (redacted) stderr and, when on, its full instructions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

Read-only tools (servers, info) are clearly separated from state-changing ones (enable, disable, restart), and servers vs info differ by scope (all servers vs one server). The only mild overlap is restart, which subsumes disable+enable, but its description explicitly distinguishes the behavior when the server is already on vs off.

Naming Consistency4/5

All names are single lowercase words with no prefixes or mixed casing, so the style is predictable. There is a minor verb/noun split (enable/disable/restart vs servers/info), though it correlates sensibly with mutating vs read-only operations.

Tool Count5/5

Five tools is exactly the lifecycle surface this server needs: list, inspect, start, stop, and restart. Every tool earns its place with no filler or redundant variants.

Completeness4/5

The full lifecycle is covered (servers, info, enable, disable, restart), including policy and sign-in states, and info surfaces stderr and instructions. Minor gaps remain: there is no way to inspect or change a server's policy, and no way to register/install a new hosted server definition.

Maintenance

ActivityNo data
ResponsivenessOutdated data