skeleton-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_ADDR | Yes | Vault server address | |
| POSTGRES_DB | Yes | PostgreSQL database name | |
| VAULT_TOKEN | Yes | Vault authentication token | |
| POSTGRES_HOST | Yes | PostgreSQL host | |
| POSTGRES_PORT | Yes | PostgreSQL port | |
| POSTGRES_USER | Yes | PostgreSQL user | |
| VAULT_KV_MOUNT | Yes | Vault KV mount path | |
| MCP_SERVER_NAME | No | Name of the MCP server | |
| POSTGRES_PASSWORD | Yes | PostgreSQL password | |
| MCP_ADMIN_AUTH_KEY | No | Authentication key for mutating tools (optional) | |
| MCP_SERVER_VERSION | No | Version of the MCP server | |
| MCP_ALLOW_SENSITIVE_OUTPUT | No | If true, sensitive fields are not redacted in tool output | false |
| VAULT_WRITE_RETRY_ATTEMPTS | No | Number of retry attempts for Vault writes | |
| VAULT_WRITE_RETRY_MAX_DELAY_MS | No | Maximum delay in ms for Vault write retries | |
| VAULT_WRITE_RETRY_BASE_DELAY_MS | No | Base delay in ms for Vault write retries |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connection_infoB | Return MCP server, Vault, and Postgres connection information with secret-safe values. |
| healthcheckA | Run connectivity checks for Postgres and Vault. |
| list_configsA | List configuration records from Postgres, optionally filtered by key prefix. |
| get_configC | Read a configuration value from Postgres by key. |
| set_configC | Create or update a configuration value in Postgres. |
| delete_configC | Delete a configuration value from Postgres by key. |
| vault_connection_infoA | Return active Vault configuration without exposing secret values. |
| list_secretsC | List child keys under a Vault path prefix. |
| get_secretC | Read a secret from Vault KV v2 by path. |
| set_secretC | Create or update a Vault secret at path. |
| delete_secretC | Delete a Vault secret at path. |
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 11 tools
Each tool targets a distinct resource and action: config operations, secret operations, connection info, and healthcheck. There is no overlap or ambiguity.
All tool names follow the consistent verb_noun pattern in snake_case (e.g., delete_config, list_secrets). Even connection_info and healthcheck fit the style.
11 tools are well-scoped for a server managing configurations and secrets across two backends, with connection info and healthcheck. Neither too many nor too few.
Full CRUD for configs and secrets (get, set, delete, list), plus connection info and healthcheck. No missing operations for the domain.