wicked-brain-mcp
The MCP server for Wicked Brain: a plain-markdown memory vault that your AI agents can search, read and write. The vault is a folder of markdown files on your machine. No account, no telemetry, nothing uploaded.
This package gives any MCP client the 12 vault tools (search, read, save, capture, update, patch, move, validate, backlinks, health, and the skill list). For the slash commands, hooks and dashboard, install the full Wicked Brain plugin for Claude Code or Codex instead.
Run it
You need uv. Point the server at your vault folder:
WICKED_BRAIN_VAULT_PATH=/path/to/vault uvx wicked-brain-mcp
MCP client config
{
"mcpServers": {
"wicked-brain": {
"command": "uvx",
"args": ["wicked-brain-mcp"],
"env": { "WICKED_BRAIN_VAULT_PATH": "/path/to/vault" }
}
}
}
Codex (~/.codex/config.toml):
[mcp_servers.wicked-brain]
command = "uvx"
args = ["wicked-brain-mcp"]
env = { WICKED_BRAIN_VAULT_PATH = "/path/to/vault" }
Your vault
The vault is just a folder of markdown files. Create it anywhere and point
WICKED_BRAIN_VAULT_PATH at it. For free version history, make it a git repository:
mkdir ~/vault && cd ~/vault && git init
Wicked Brain never deletes notes and never overwrites an existing one, but git lets you review or undo any change an agent makes.
Tools
Read-only: brain_search, brain_read_note, brain_validate_note, brain_backlinks,
brain_vault_health, brain_list_skills, brain_get_skill.
Additive (never overwrite): brain_save_note, brain_capture.
Edit existing notes (destructive hint): brain_update_note, brain_replace_text, brain_move_note.
All tools stay inside the vault folder. See the repository for the vault layout and the optional end-to-end-encrypted sync.
MIT licensed.
Metadata
Release files for wicked-brain-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wicked_brain_mcp-0.1.1.tar.gz | 106.3 kB | Without provenance | Details for wicked_brain_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wicked_brain_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for wicked_brain_mcp-0.1.1-py3-none-any.whl |
Total release size: 231.6 kB
Release files / wicked_brain_mcp-0.1.1.tar.gz
| Download URL | wicked_brain_mcp-0.1.1.tar.gz |
|---|---|
| Size | 106.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04ecc5f7a2e6bc29b03c3ef2f5177f398134d133573c07a1e24349196a32e406
|
|
BLAKE2b-256 checksum How to use checksums |
22ac3c4ab535940dbdc4e7f2f795108670ed165da3a8f756336d16758ae0360e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.5 {"installer":{"name":"uv","version":"0.10.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / wicked_brain_mcp-0.1.1-py3-none-any.whl
| Download URL | wicked_brain_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 125.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3c7e4f7b6c36b095bdf4c7155a1aa27719d99254ade8039fdeaa9deb9c577e6e
|
|
BLAKE2b-256 checksum How to use checksums |
08684751fe86bdb06347a460cd746e4608a44f15af02df78f43fcee779d26119
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.5 {"installer":{"name":"uv","version":"0.10.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for wicked-brain-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.