claude-secrets
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_secretA | Read a secret value by name. Requires name to be whitelisted in project .claude/secrets.yml. |
| set_secretA | Store a secret value. Creates or overwrites. Requires name to be whitelisted in project .claude/secrets.yml. |
| list_secretsA | List secret names visible to current project (filtered by .claude/secrets.yml allowlist). |
| delete_secretA | Delete a secret by name. Requires allowlist. |
| search_secretsA | Search secret names by regex pattern (case insensitive). Filtered by allowlist. |
| input_secretA | Prompt the user for a secret value via a native macOS dialog (hidden input), then store it. The value never passes through the model or the chat — it goes directly from the user's dialog into the encrypted store. Use this when you need a token, password, or API key the user has not yet stored. Requires name to be whitelisted in project .claude/secrets.yml. |
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 6 tools
Each tool targets a distinct action on secrets (delete, get, input, list, search, set) with no overlap. An agent can clearly distinguish between them.
All tools follow a consistent verb_secret pattern using snake_case, making them predictable and easy to understand.
Six tools cover the essential operations for secret management—CRUD plus search and user input—without being excessive or insufficient.
The set covers the full lifecycle of secrets: create/update (set), read (get), delete, list, search, and user input. There are no obvious gaps for a basic secret store.