memorylens-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_processesA | Lists running .NET processes suitable for memory profiling, discovered from their diagnostic IPC endpoints. Excludes IDE, tooling, and MCP server processes to prevent interference. |
| snapshotA | Takes a memory snapshot of a running .NET process. Provide a pid. Returns a snapshot id to pass to analyze. |
| get_rulesA | Lists all active analysis rules with their ID, title, severity, and category. Rules can be configured via .memorylens.json in the project root. |
| compare_snapshotsA | Takes two memory snapshots of a .NET process with a delay between them for comparison. Useful for detecting memory leaks by comparing before/after state. Provide a pid. Returns the ids and paths of both snapshots. |
| analyzeB | Analyzes a memory snapshot using built-in rules to detect leaks, fragmentation, excessive allocations, and anti-patterns. Returns findings with severity, description, and optional code suggestions. |
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 targets a distinct phase of the profiling workflow (discovery, snapshot, comparison, analysis, rule listing), and descriptions are clear enough to avoid serious misselection. However, snapshot and compare_snapshots both involve taking snapshots; while not ambiguous in intent, they are closely related.
Most names follow a verb_snake_case pattern (list_processes, get_rules, compare_snapshots), but 'snapshot' and 'analyze' are single-word verbs rather than the verb_noun form. The naming is readable but not perfectly uniform across the set.
Five tools is well-scoped for a memory profiling MCP server. Each tool serves a necessary part of the primary workflow, and there is no bloat or redundancy.
The tool set covers the core workflow: find process, take snapshot, compare snapshots, analyze against rules, and list rules. Minor gaps like managing rules directly or inspecting snapshot raw details are missing, but the main user journeys are supported.