mcp-memory-server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_memory_usageA | Get system memory usage summary. Returns total, available, used memory and swap statistics,
similar to the |
| list_top_processesC | List top N memory-consuming processes. |
| list_process_groupsA | List processes grouped by name with aggregated stats. Useful for seeing total resource usage by process type (e.g., "3 claude processes using 1.6GB total"). |
| find_stale_processesB | Find potentially stale processes based on various criteria. Useful for finding long-running background processes that may be consuming resources unnecessarily. |
| kill_processesA | Kill processes by PID with safety checks. Safety mechanisms:
|
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 5 tools
Each tool has a distinct purpose: memory usage overview, top processes, process grouping, stale process detection, and process termination. Even the two listing tools are clearly differentiated by their focus on top consumers versus name-based aggregation, with descriptions reinforcing this.
All tool names follow a consistent verb_noun pattern in snake_case (list_*, find_*, kill_*). There are no mixed conventions or vague verbs, making the API predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose. It provides a comprehensive set for memory monitoring and process management without unnecessary bloat, and each tool earns its place.
The tool surface covers the core lifecycle: memory overview, process listing, grouping, stale detection, and killing. A minor gap is the lack of a tool to retrieve detailed information about a single process by PID, but this does not critically impede the server's primary functionality.