MCP Memory Server vs Sentry MCP

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	MCP Memory Server MCP Servers	Sentry MCP MCP Servers
Tagline	Persistent knowledge-graph memory for Claude and other MCP clients	Official Sentry MCP server: give Claude Code, Cursor, and other AI agents real access to your errors, traces, and triage.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Self-hosted; no vendor charges. Runs locally via npx or Docker.	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month
Model	—	Bring-your-own LLM (OpenAI, Anthropic, Azure OpenAI, or OpenRouter) for natural-language search skills; agent-side model is whatever your MCP client runs.
Editorial score	—	—
Use cases	Persistent Claude Desktop memory across chatsLong-lived coding-agent project memoryLightweight personal CRM of people and companiesResearch-agent scratch knowledge graphCross-session preference and style memoryTeam convention and past-bug recall for coding assistantsStructured note-taking backend for MCP clientsLocal-first alternative to hosted memory APIs	Debug production error from IDE agentRoot-cause a latency regression via trace lookupTriage new issues (assign, resolve, comment) from chatCorrelate a failing test with recent Sentry eventsNatural-language search across eventsPost-deploy error-rate investigationPull stack trace and open the offending file for a fixSummarize top issues for a standupQuery self-hosted Sentry from an internal coding agent
Pros	Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB Nine well-scoped tools plus a live-updating knowledge-graph Resource, so agents can both read and mutate memory Fully open source (MIT) and vendor-neutral - runs against any MCP-speaking model, not just Claude Trivial to fork or wrap for team-specific schemas since the codebase is a single small TypeScript file	Official first-party server from Sentry — kept in step with API changes, not a community wrapper Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx Works with self-hosted Sentry, not only sentry.io One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector Fine-grained skill toggles let you scope which tools the agent can call Covers the full debugging loop: issues, events, traces, search, and triage actions like assign/resolve/comment Open source, so the tool surface and prompts can be audited or extended
Cons	Reference-quality, not production-grade: single-file JSONL storage with no concurrency control, indexing or replication search_nodes is a plain substring match with no embeddings or semantic ranking - large graphs degrade quickly No built-in multi-user, auth or per-project isolation; a shared install mixes memories from every session The model still has to be prompted to actually call the memory tools - forgetful assistants forget to remember No web UI, visualisation or admin surface; you inspect and clean the graph by editing the JSONL yourself Only a local filesystem backend - no Postgres, SQLite or cloud sync option is shipped	You still need a paid Sentry plan to get useful volumes of events, retention, and org seats Natural-language search tools require you to bring your own OpenAI/Anthropic/Azure/OpenRouter key — extra cost and setup Value collapses if your team is not already invested in Sentry as its error/APM backend Remote server is single-tenant per token — sharing across a team means each engineer wires their own auth MCP itself is still young; some clients handle remote servers with headers imperfectly and stdio is often the fallback Read/write tools mean a misbehaving agent can resolve or reassign real issues — human-in-the-loop is not optional
Website	github.com	github.com

Pick MCP Memory Server if

✅ Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
✅ Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
✅ Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
✅ Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB

Pick Sentry MCP if

✅ Official first-party server from Sentry — kept in step with API changes, not a community wrapper
✅ Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx
✅ Works with self-hosted Sentry, not only sentry.io
✅ One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector

Compare a different pair →