mcp-apollo-config
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APOLLO_OPERATOR | No | Operator name (required in editable mode) | |
| APOLLO_PASSWORD | Yes | Password for Apollo portal login | |
| APOLLO_USERNAME | Yes | Username for Apollo portal login | |
| APOLLO_PORTAL_URL | Yes | URL of Apollo portal | |
| APOLLO_TIMEOUT_MS | No | Timeout in milliseconds | 10000 |
| APOLLO_DEFAULT_ENV | No | Default environment (e.g., DEV, TEST) | |
| APOLLO_LOGIN_SUBMIT | No | Login submit endpoint (optional) | |
| MCP_APOLLO_LOG_LEVEL | No | Log level: DEBUG, INFO, WARN, ERROR | WARN |
| APOLLO_DEFAULT_APP_ID | No | Default app ID | |
| MCP_APOLLO_DEBUG_HTTP | No | Enable HTTP debug logging (true/false) | |
| APOLLO_DEFAULT_CLUSTER | No | Default cluster | default |
| APOLLO_GOVERNANCE_MODE | No | Governance mode: readonly or editable | readonly |
| APOLLO_DEFAULT_NAMESPACE | No | Default namespace | application |
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
| Name | Description |
|---|---|
| apollo_get_namespace_configsC | Query all configs under a namespace/environment/cluster in Apollo. |
| apollo_get_keyC | Query a single key in a namespace/environment/cluster in Apollo. |
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
The two tools have clearly distinct purposes: one retrieves a single key, the other retrieves all configs under a namespace. No overlap in functionality.
Both tools follow a consistent 'apollo_get_<thing>' pattern in snake_case, making it predictable and easy to understand.
With only 2 tools, the surface is thin but appropriate for a read-only query interface focused on single key and full namespace config retrieval.
The server lacks any write operations (create, update, delete) and only provides basic read capabilities. Significant gaps exist for managing configurations.