Persistent memory for AI agents — audio intelligence + Music Memory ingestion and recall
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y bluecolumn-mcp
MCP client config
{
"mcpServers": {
"bluecolumn-memory": {
"command": "npx",
"args": [
"-y",
"bluecolumn-mcp"
]
}
}
}Give Claude Desktop, Cursor, and any MCP-compatible agent persistent memory across sessions.
2-minute setup. Zero-config. Audio-native. Works with every MCP client.
MCP server for BlueColumn — persistent semantic memory for AI agents.
Give any MCP-compatible agent (Claude Desktop, Cursor, Windsurf, LangChain, AutoGen, CrewAI) the ability to remember, recall, and store observations across sessions.
| Tool | Description |
|---|---|
remember | Ingest text, audio, or documents into persistent memory |
recall | Query memory with natural language, get AI-synthesized answer + sources |
note | Store lightweight agent observations as searchable vectors |
namespace | Show the configured namespace |
| Tool | Description |
|---|---|
music_remember | Store a musical recording, practice session, or lesson with rich musical context — instrument, key, tempo, technique tags, chord progression, notes. Audio is transcribed; the structured context is embedded alongside so a coach/teacher agent recalls it with full musical understanding |
music_recall | Search stored musical content with musical filters — instrument, technique, or style. E.g. "show me every take with barre chord issues" or "what did we practice in E minor last month" |
| Tool | Description |
|---|---|
audio_ingest | Ingest calls, voice notes, podcasts, meetings, or music and extract semantic memory |
audio_recall | Search audio memories and get audio-backed citations |
call_prepare | Get memory context before a voice call starts |
call_complete | Store what changed after a call ends |
sound_analyze | Detect and index non-speech audio events |
music_analyze | Extract tempo, structure, instrumentation, mood from music |
| Tool | Description |
|---|---|
streaming_audio_ingest | Ingest edge-device audio chunks (car, doorbell, wearable) into per-device streaming memory |
streaming_audio_recall | Recall over a device's streamed audio history |
Store a practice session:
music_remember {
"audio_url": "https://example.com/take3.mp3",
"title": "Week 3 practice — barre chords, Sep 7",
"instrument": "guitar",
"musical_key": "E minor",
"tempo_bpm": 92,
"technique_tags": ["barre-chords", "hammer-on"],
"style_tags": ["blues"],
"chord_progression": ["Em", "Am", "B7"],
"notes": "F-shape barre still buzzy on the B string; Fmaj7 subst worked well"
}
Then recall it musically:
music_recall { "q": "which takes had barre chord issues?", "instrument": "guitar" }
Sign up free at bluecolumn.ai — 60 min audio + 100 queries/month, no credit card required.
npm install -g bluecolumn-mcp
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"bluecolumn": {
"command": "bluecolumn-mcp",
"env": {
"BLUECOLUMN_API_KEY": "bc_live_YOUR_KEY"
}
}
}
}
Done. Claude now remembers everything you tell it to.
| Feature | BlueColumn MCP | Other MCP Memory Servers |
|---|---|---|
| Audio ingestion | ✅ Native (transcribe + store) | ❌ Text only |
| Plain English recall | ✅ "What did we decide about pricing?" | ❌ Keyword/vector only |
| Setup time | ~2 minutes | ~10-30 minutes |
| Cloud managed | ✅ No infra to run | ⚠️ Most require local DB |
| Namespace isolation | ✅ Built-in per key | ⚠️ Manual |
Remember: We're building a React component library called Aether with Tailwind CSS v4.
What project was I working on? What was my tech stack?
→ Claude recalls: "You're building Aether, a React component library with Tailwind CSS v4"
Record a voice memo → BlueColumn transcribes it → Claude remembers it.
{
"mcpServers": {
"bluecolumn": {
"command": "bluecolumn-mcp",
"env": {
"BLUECOLUMN_API_KEY": "bc_live_YOUR_KEY",
"BLUECOLUMN_NAMESPACE": "my_project"
}
}
}
}
Use different namespaces for work, personal, and side projects. Each stays isolated.