meMCP - Memory-Enhanced Model Context Protocol
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
The tools are organized into clear configuration and memory domains, but there is some ambiguity within each group. For example, config_export and config_validate have unclear boundaries, and memory_stream_* tools could be confused for overlapping streaming operations. Descriptions are missing, making it harder to differentiate, but the prefix structure helps.
All tool names follow a consistent snake_case pattern with clear prefixes (config_* and memory_*). The naming is highly predictable and organized, making it easy to understand the tool's domain and purpose at a glance.
With 24 tools, the count feels excessive for a memory-enhanced protocol. Many tools seem redundant or overly granular (e.g., multiple memory_stream_* actions), suggesting the set could be consolidated without losing functionality. This heavy tool count may overwhelm agents.
The tool set appears to cover core memory and configuration operations comprehensively, including CRUD-like actions (store, delete, update, query) and management functions (backup, restore, optimize). Minor gaps might exist in advanced querying or integration features, but the surface seems well-rounded for the inferred domain.