Skip to main content
Glama
wb200

Memory-MCP

by wb200
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EMBEDDING_DIMNoEmbedding dimensions1024
GOOGLE_API_KEYNoGoogle Gemini API key (required if using Google as embedding provider or for LLM judge)
EMBEDDING_MODELNoEmbedding model nameqwen3-embedding:0.6b
OLLAMA_BASE_URLNoOllama API endpointhttp://localhost:11434
EMBEDDING_PROVIDERNoEmbedding provider to use: 'ollama' or 'google'ollama
LANCEDB_MEMORY_PATHNoDatabase location for storing memories~/.memory-mcp/lancedb-memory

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_saveA

Save a memory with semantic embedding. Use after learning something valuable.

Args:
    content: Memory content. Format: '[CATEGORY] - [insight]. Context: [where]. Rationale: [why]'
    category: One of PATTERN, CONFIG, DEBUG, PERF, PREF, INSIGHT, API, AGENT
    tags: Optional tags for categorization (auto-extracted if summarize=True)
    summarize: Use LLM to intelligently summarize verbose content
memory_recallA

Hybrid search (vector + BM25) across ALL projects with neural reranking.

Args:
    query: Search query - works with both keywords and semantic concepts
    category: Optional filter: PATTERN, CONFIG, DEBUG, PERF, PREF, INSIGHT, API, AGENT
    limit: Max results (default 5, max 50)
memory_recall_projectA

Hybrid search in CURRENT project only with neural reranking.

Args:
    query: Search query - works with both keywords and semantic concepts
    category: Optional category filter
    limit: Max results (default 5, max 50)
memory_deleteA

Delete a memory by ID.

Args:
    memory_id: The ID of the memory to delete (full or partial UUID)
memory_updateA

Update an existing memory.

Args:
    memory_id: The ID of the memory to update (full or partial UUID)
    content: New content (re-embeds if changed)
    category: New category
    tags: New tags (replaces existing)
memory_statsA

Get memory system statistics - total, by category, by project.

memory_healthA

Get memory system health status - indexes, database size, configuration.

memory_session_startA

Get project context at session start: recent memories + AI summary.

Call this at the start of a session to recall project-specific context.
Includes:
- Project Highlights summary (architecture, tech stack, setup, patterns)
- Last 10 memories for immediate context

Use this instead of manually recalling memories.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
memory_stats_resourceMemory statistics as a read-only resource.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a distinct purpose: delete, health, recall (all projects), recall (current project), save, session start, stats, update. The two recall tools are differentiated by scope, and no overlapping functionality exists.

Naming Consistency5/5

All tools follow a consistent 'memory_<verb>' pattern in snake_case, with verbs like delete, recall, save, update. The compound 'session_start' still fits the pattern clearly.

Tool Count5/5

8 tools is appropriate for a memory system, covering CRUD operations, search, health, stats, and session context. Each tool earns its place without being excessive.

Completeness4/5

Core CRUD is covered (save, recall, update, delete). Minor gaps: no direct retrieval of a single memory by ID (only recall with search) and no bulk operations. Agents can work around these gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources