Bluecolumn Memory

io.github.bluecolumnconsulting-lgtmPublished by GitHub account bluecolumnconsulting-lgtmv1.4.0Updated Oct 26, 2026

Persistent memory for AI agents — audio intelligence + Music Memory ingestion and recall

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & MemoryMedia & Design

Overview

AI-generated overview

BlueColumn Memory gives an MCP agent persistent semantic memory across sessions, including ingestion and recall of audio, calls, and music.

What you can do
  • Store and recall text, documents, and observations in persistent memory with natural-language queries and cited answers
  • Ingest audio such as calls, voice notes, meetings, podcasts, and music, then search it with audio-backed citations
  • Capture and query musical practice sessions by instrument, key, tempo, technique, and style tags
  • Prepare context before a voice call and record what changed after it ends
  • Analyze non-speech sound events and extract tempo, structure, instrumentation, and mood from music
  • Ingest and recall streamed audio chunks from edge devices such as cars, doorbells, or wearables
When to use it
Useful when you want an assistant to remember project context, decisions, or notes between conversations without running your own database, and when you want voice memos, calls, or music practice sessions to become searchable memory.
Requirements
Runs locally as an npm package (bluecolumn-mcp) over stdio, typically configured in a desktop MCP client. Requires a BlueColumn API key in BLUECOLUMN_API_KEY; a free tier is offered. BLUECOLUMN_API_URL optionally points at the API base, defaulting to a local backend at localhost:8000. Network access to the BlueColumn service is needed.
Before you install
The API key in BLUECOLUMN_API_KEY is a credential and should be kept out of shared config files. Content you store, including audio and transcripts, is sent to a third-party cloud service for transcription and embedding. Memory writes persist across sessions and are isolated per namespace, so check which namespace is configured before storing sensitive material.

Installation

In SourceWeft

  1. Open Bluecolumn Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

🧠 BlueColumn MCP Server

Give Claude Desktop, Cursor, and any MCP-compatible agent persistent memory across sessions.

[npm version] [License] [BlueColumn]

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.

Tools

Core memory

ToolDescription
rememberIngest text, audio, or documents into persistent memory
recallQuery memory with natural language, get AI-synthesized answer + sources
noteStore lightweight agent observations as searchable vectors
namespaceShow the configured namespace

Music Memory (new)

ToolDescription
music_rememberStore 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_recallSearch 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"

Audio Intelligence

ToolDescription
audio_ingestIngest calls, voice notes, podcasts, meetings, or music and extract semantic memory
audio_recallSearch audio memories and get audio-backed citations
call_prepareGet memory context before a voice call starts
call_completeStore what changed after a call ends
sound_analyzeDetect and index non-speech audio events
music_analyzeExtract tempo, structure, instrumentation, mood from music

Streaming audio memory

ToolDescription
streaming_audio_ingestIngest edge-device audio chunks (car, doorbell, wearable) into per-device streaming memory
streaming_audio_recallRecall over a device's streamed audio history

Music Memory example

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" }

Setup

1. Get your BlueColumn API key

Sign up free at bluecolumn.ai — 60 min audio + 100 queries/month, no credit card required.

2. Install

bash
npm install -g bluecolumn-mcp

3. Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "bluecolumn": {      "command": "bluecolumn-mcp",      "env": {        "BLUECOLUMN_API_KEY": "bc_live_YOUR_KEY"      }    }  }}

4. Restart Claude

Done. Claude now remembers everything you tell it to.

What Makes BlueColumn Different

FeatureBlueColumn MCPOther 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

Examples

Store project context

Remember: We're building a React component library called Aether with Tailwind CSS v4.

Recall across sessions (new conversation)

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"

Store audio notes

Record a voice memo → BlueColumn transcribes it → Claude remembers it.

Advanced

Custom namespace

json
{  "mcpServers": {    "bluecolumn": {      "command": "bluecolumn-mcp",      "env": {        "BLUECOLUMN_API_KEY": "bc_live_YOUR_KEY",        "BLUECOLUMN_NAMESPACE": "my_project"      }    }  }}

Multiple environments

Use different namespaces for work, personal, and side projects. Each stays isolated.


Sign up free → · Docs · GitHub Issues

Source: README.md at commit 871a2bc

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.4.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations