Skip to main content
Glama

🧠 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

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

Music Memory (new)

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"

Audio Intelligence

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

Streaming audio memory

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

Related MCP server: hypermnesia

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

npm install -g bluecolumn-mcp

3. Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.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

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

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

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

Available Tools

10 tools
audio_ingestC

NEW (Audio Intelligence): Ingest audio (calls, voice notes, podcasts, music) and extract semantic memory using the audio-intelligence layer. Requires BLUECOLUMN_API_URL to point at the BlueColumn API.

Inputs: audio_url (required), customer_id (required), source_type (required), metadata.

audio_recallC

NEW (Audio Intelligence): Search audio memories and get audio-backed citations.

Inputs: customer_id (required), query, top_k, filter_type.

call_completeB

NEW (Audio Intelligence): Store what changed after a call ends.

Inputs: call_id (required), customer_id (required), new_memories, follow_up_required, +1 more.

call_prepareB

NEW (Audio Intelligence): Get memory context before a voice call starts.

Inputs: customer_id (required), include.

music_analyzeC

NEW (Audio Intelligence): Extract tempo, structure, instrumentation, mood from music.

Inputs: audio_id (required), extract.

namespaceA

Get the BlueColumn namespace this MCP server is configured to write/read (default: nl).

Inputs: no named parameters.

noteA

Store a lightweight agent observation as a searchable vector. Use when the agent wants to save a quick preference, decision, or observation without needing full document processing. Faster than remember for short notes.

Inputs: text (required), tags.

recallA

Query BlueColumn memory using natural language. Returns an AI-synthesized answer with source citations. Use when the agent needs to retrieve past information, answer questions about stored content, or get context from previous sessions.

Inputs: q (required).

rememberA

Store text, a document URL, or audio URL into BlueColumn persistent memory. Returns a summary, action items, and key topics automatically extracted by AI. Use when the user or agent wants to save information for future recall.

Inputs: text, title, file_url, audio_url.

sound_analyzeC

NEW (Audio Intelligence): Detect and index non-speech audio events.

Inputs: audio_id (required), search_for, detect_events.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 10 tools

    Disambiguation3/5

    Tools like note, remember, call_complete, and audio_ingest all store information, with subtle distinctions that could lead to misselection. recall and audio_recall also overlap, though audio_recall is more specific.

    Naming Consistency2/5

    Names mix conventions: some are verbs (remember, recall), some are noun_verb (audio_ingest, sound_analyze), and some are verb-like but structured as object+verb (call_prepare, call_complete). No consistent pattern.

    Tool Count4/5

    10 tools is a reasonable count for the server's apparent scope. While a few tools feel peripheral (sound_analyze, music_analyze), the overall number is not excessive.

    Completeness3/5

    The server covers storage and retrieval well, including audio-specific features. However, there is no delete or update operation for memories, which is a notable gap in lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, searchable memory for MCP-compatible agents, enabling recall by meaning, automatic decay, trust scoring, and cross-agent handoffs.
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.
      4
      1
      MIT