Skip to main content
Glama
MikSkrzyp

identity-storage-mcp

by MikSkrzyp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IDENTITY_STORAGE_DBNoSQLite database file path~/.identity-storage/memory.db

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_searchA

Search past memories by content. Call this when the user references past work ('do you remember', 'last time', 'previously') or when you need context from a previous session. Pass the user's prompt as query. Returns ranked results from FTS5. If empty, no memory is needed for this turn. For browsing by tags or time window, use memory_recall.

memory_storeA

Store a memory. You MUST call this after every non-trivial turn. Choose the type based on what you are saving:

  • episodic: an event that happened — 'fixed the login bug in auth.py', 'user asked for a tic-tac-toe game', 'refactored auth module to use JWT'. Concrete actions and outcomes.

  • semantic: a durable fact that stays true — 'user prefers Python 3.12', 'project uses pytest', 'auth uses JWT', 'user communicates in Polish'. Knowledge about the user or project.

  • procedural: a how-to with steps — 'run tests with pytest -x', 'deploy via npm run build && rsync', 'start dev server: python -m backend.main'. Steps to accomplish something.

Set confidence below 1.0 for inferences, assumptions, or guesses. Use tags for filtering (e.g. project name, topic). Episodic payload keys: session_id, agent, task, outcome, parent_id, metadata. Store one memory per distinct thing. ALWAYS skip idle chat, greetings, and trivial responses. Forgetting to store = permanent loss of the session.

memory_recallA

Browse memories of one type, newest first. Filter by tags and time window. Use for 'what did I do recently' or 'what happened in this session'. Not for per-turn recall — use memory_search for that.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: memory_recall for browsing by tags/time, memory_search for content search, and memory_store for saving memories. No ambiguity between them.

Naming Consistency5/5

All tools follow a consistent 'memory_' prefix with a verb (recall, search, store), making the tool names predictable and easy to understand.

Tool Count4/5

With 3 tools, the set feels slightly minimal but appropriate for a targeted memory storage and retrieval system. The count is reasonable for the scope.

Completeness3/5

The tool surface covers storing and two retrieval methods, but lacks delete or update operations, which are notable gaps for a complete memory lifecycle.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources