Memorylens Mcp
Profile .NET memory usage from your agent via JetBrains dotMemory-backed MemoryLens MCP instead of manually opening snapshots in the IDE.
Overview
MemoryLens MCP is an MCP server for the Ship phase that brings JetBrains dotMemory-style .NET memory profiling into agent tool calls over stdio.
What is this MCP server?
- NuGet package MemoryLens.Mcp v1.3.4 with stdio MCP transport
- Integrates JetBrains dotMemory workflows for .NET heap and allocation insight
- dnx runtime hint for modern .NET tool execution from the MCP host
- Lets coding agents request profiling context without leaving the terminal session
- Open-source server at github.com/MarcelRoozekrans/memorylens-mcp
- Package version 1.3.4 on NuGet identifier MemoryLens.Mcp
- Registry base NuGet.org v3 API
Community signal: 3 GitHub stars.
What problem does it solve?
.NET memory issues are hard to explain to an agent when profiling lives only inside JetBrains desktop workflows.
Who is it for?
.NET indie developers who already use or can install dotMemory and want MCP-assisted leak hunts before ship.
Skip if: JavaScript-only stacks, teams without JetBrains profiling tooling, or builders who only need HTTP APM metrics.
What do I get? / Deliverables
After you add MemoryLens.Mcp to MCP config, your agent can drive dotMemory-integrated memory analysis as part of perf fixes.
- Agent-accessible .NET memory profiling session via MemoryLens
- dotMemory-aligned insights for allocation and retention issues
- Repeatable perf investigation workflow before release
Recommended MCP Servers
Journey fit
How it compares
.NET memory-profiling MCP with dotMemory integration, not a full production APM suite.
Common Questions / FAQ
Who is MemoryLens MCP for?
Solo builders and small teams on .NET who use MCP-enabled agents and JetBrains dotMemory for serious memory diagnosis.
When should I use MemoryLens MCP?
Use it in Ship perf work—or Operate when investigating regressions—when allocations, retained objects, or GC spikes threaten stability.
How do I add MemoryLens MCP to my agent?
Register the NuGet tool MemoryLens.Mcp with stdio transport, ensure dnx/.NET runtime is available to the MCP host, install dotMemory prerequisites per the repo README, then restart your client.