Skip to main content
Glama
gabrimatic

mcp-prose-memory

by gabrimatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMORY_PATHNoOverride the default memory storage path (~/.mcp-prose-memory/memory.json)

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

Tools

Functions exposed to the LLM to take actions

NameDescription
memoryA

Manage persistent memory across sessions.

Commands:

  • view: Show all memories (optionally filter by section)

  • add: Add a new fact to a section

  • upsert: Add or replace a structured fact by key

  • remove: Remove a fact by section and line number

  • replace: Update a fact by section and line number

Sections: work, personal, top_of_mind, history, instructions, user_profile, user_preferences, eyra_project, devices_environment, workflows, writing_style, long_term_tasks, do_not_forget

Examples:

  • {"command": "view"}

  • {"command": "view", "section": "work"}

  • {"command": "add", "section": "personal", "fact": "Lives in Berlin"}

  • {"command": "upsert", "section": "user_preferences", "key": "answer_style", "value": "Prefers concise answers"}

  • {"command": "remove", "section": "work", "line": 3}

  • {"command": "replace", "section": "top_of_mind", "line": 1, "fact": "Working on new project"}

memory_contextA

Load memory for session start. Supports compact bounded context for clients with small prompt budgets.

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

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'memory' handles CRUD operations on memories, while 'memory_context' loads memory for session start. No overlap or ambiguity.

Naming Consistency4/5

Both tool names start with 'memory' and use underscores for compound names, following a consistent pattern. However, 'memory' is a single noun while 'memory_context' is a compound noun, a minor deviation.

Tool Count3/5

With only 2 tools, the server is lean. All CRUD operations are bundled into one tool, which works but limits granularity. The count is on the low side but acceptable given the internal richness.

Completeness4/5

The 'memory' tool covers all standard CRUD operations (view, add, upsert, remove, replace), and 'memory_context' handles context loading. Minor gaps like listing sections or clearing all memories are missing but not critical.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources