secrets-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SECRETS_VAULT_PATH | No | The path to the markdown file containing secrets. Defaults to ~/.secrets.md if not specified. |
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 |
|---|---|
| list_sectionsB | List all section titles in the secrets vault |
| get_sectionC | Get a specific section from the secrets vault by title |
| search_secretsC | Search the secrets vault for sections matching a keyword |
| upsert_sectionC | Add or update a section in the secrets vault |
| delete_sectionC | Delete a section from the secrets vault by title |
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 5 tools
Each tool has a clearly distinct purpose: list_sections enumerates all sections, get_section retrieves a specific one, upsert_section creates or updates, delete_section removes, and search_secrets finds matches. No ambiguity exists between these operations, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with snake_case, such as list_sections, get_section, upsert_section, delete_section, and search_secrets. This uniformity enhances readability and predictability across the tool set.
With 5 tools, the server is well-scoped for managing a secrets vault, covering core operations like listing, retrieving, creating/updating, deleting, and searching. This count is appropriate, avoiding bloat while ensuring essential functionality is present.
The tool set provides complete CRUD/lifecycle coverage for sections in a secrets vault: list, get, create/update (via upsert), delete, and search. No obvious gaps exist, allowing agents to perform all typical operations without dead ends.