MCP Registry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_REGISTRY_SEED_FROM | No | Source for seed data. By default it seeds from the production API; can be set to a file path (e.g., data/seed.json) for offline development. | production |
| MCP_REGISTRY_DATABASE_URL | Yes | PostgreSQL connection string for the registry database. The registry image does not bundle PostgreSQL, so you must provide your own and point the registry to it via this variable. | |
| MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION | No | Whether to enable validation of seed data. Set to 'false' to disable validation (e.g., when seeding from a local file without validation). | true |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues