secrets-mcp
# secrets-mcp
MCP server that gives Claude Code access to your personal secrets and notes stored in a simple Markdown file (`~/.secrets.md`).
## Install
```bash
npx secrets-mcp setup
```
This will:
1. Create `~/.secrets.md` if it doesn't exist
2. Create a desktop shortcut to open it
3. Register the MCP server globally in Claude Code
## Usage
After setup, Claude Code can access your secrets from **any project** using these tools:
| Tool | Description |
|------|-------------|
| `list_sections` | List all section titles |
| `get_section` | Get a section by title |
| `search_secrets` | Search by keyword |
| `upsert_section` | Add or update a section |
| `delete_section` | Delete a section |
### Edit your secrets
Double-click **"My Secrets.bat"** on your desktop, or open `~/.secrets.md` in any editor.
### File format
Your `~/.secrets.md` is standard Markdown with sections:
```markdown
# My Secrets
## AWS
- Access Key: AKIA...
- Secret Key: wJalr...
- Region: us-east-1
## Database
- Host: db.example.com
- Password: hunter2
```
## Manual setup
If `npx secrets-mcp setup` doesn't work, register manually:
```bash
claude mcp add secrets-mcp -s user -- npx -y secrets-mcp serve
```
## How it works
- Reads `~/.secrets.md` (or `$SECRETS_VAULT_PATH`) on each tool call
- Parses Markdown headings into sections
- No encryption, no dependencies beyond the MCP SDK — just a file
## Portability
To move to a new machine:
1. Copy your `~/.secrets.md` file
2. Run `npx secrets-mcp setup`
## License
MIT
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.