Agent Registry MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REGISTRY_API_KEYS | No | Server-side API keys for roles. Example: REGISTRY_API_KEYS=member-token:MEMBER,lead-token:LEAD. MEMBER can read, search, resolve, capture, and register candidate memory. LEAD can additionally promote, deprecate, and publish governed state. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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 15 tools
Most tools clearly target a distinct resource+action pair (context/skill/project/memory/agent), and parallel search/get operations across resources are reasonably distinguishable. However, skill_resolve versus skill_get is ambiguous without descriptions, and memory_get versus memory_recent plus context_search versus context_get have overlapping retrieval semantics that an agent could easily misselect.
All 15 tools use consistent snake_case with a resource-first, action-second pattern (e.g. context_search, skill_get, memory_register, project_detect). The two *_status tools (registry_status, agent_status) fit the same resource_action convention rather than deviating from it.
15 tools is at the upper end but well-scoped for a registry spanning six resource domains (context, skill, project, memory, registry, agent), with roughly 2-3 tools per domain and no obvious redundancy.
The surface covers registration, lookup, and search for some resources, and memory has a full lifecycle including memory_transition. But there is no skill_register, no context_register, no update/delete operations for projects or contexts, and agent support is limited to a single status tool, leaving notable lifecycle gaps.