Problemsby GlyphTrouble with Model Context Protocol memory
4 posts from 3 people3d activeSteady, +2 this week
Posts per day
The posts behind it
Tracker: Memory v2.3.0
## Summary Tracks the `memory` server work that ships in **v2.3.0**. ## Sub-issues - #5202 memory: say when to use read_graph, search_nodes and open_nodes in their descriptions - #5201 memory: add_observations stores a repeated observation twice when it appears twice in one call...
Tracker: Memory v2.2.0
## Summary Tracks the `memory` server work that ships in **v2.2.0**. ## Sub-issues - #5203 memory: a failed memory.json to memory.jsonl migration is silently ignored - #5058 memory: create_entities / create_relations / add_observations are marked non-destructive but drop data...
memory: create_entities, create_relations and add_observations could declare idempotentHint: true
...### Alternatives or workarounds you have tried Leaving it as is is safe: clients just retry less than they could. A client could hardcode a per-tool override, but that defeats the purpose of declaring hints on the server. ### Already built it locally? No local change, so no...
memory: delete tools report success when nothing matched
`delete_entities`, `delete_observations` and `delete_relations` return `success: true` with a hardcoded message regardless of what matched. `src/memory/index.ts`: The method returns `void`, so the handler never learns whether a name existed. A call naming an entity that is not...
Companies and products named
About this problem
Evidence
4 posts from 3 people in 1 place, about 1 a week over 54 days. Mostly on modelcontextprotocol/servers. Tools named alongside: GitHub.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Model Context Protocol with no known issue, sharing the word "memory". First post Sep 2, 2026, latest Oct 25, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other Model Context Protocol problems
Model Context Protocol users keep filing bugs
Top post: "issue: Realtime voice unable to invoke MCP tools", one of 41 posts from 16 people on GitHub issues, Reddit.
Model Context Protocol upgrades break working setups
12 posts from 11 people on GitHub issues, Reddit.
Trouble with Model Context Protocol server
Top post: "MCP Server Trigger v2: tools/call right after session re-initialize succeeds but response is never delivered", one of 9 posts from 7 people on GitHub issues.
Model Context Protocol rate limits and usage caps block work
6 posts from 5 people on GitHub issues, Hacker News.
Model Context Protocol vulnerabilities are hard to triage and patch
5 posts from 5 people on Glyph Ibis, GitHub issues.
Model Context Protocol fails to return valid structured output
5 posts from 5 people on GitHub issues, Reddit.
Model Context Protocol tables suffer from small files and skew
3 posts from 2 people on GitHub issues.
Trouble with Model Context Protocol session
Top post: "everything: Streamable HTTP answers 400 instead of 404 for an unknown or terminated session", one of 3 posts from 2 people on GitHub issues.
Prompt injection makes Model Context Protocol features unsafe
2 posts from 2 people on GitHub issues. Unverified.
Model Context Protocol compute costs spiral out of control
2 posts from 1 person on GitHub issues. Unverified.
Model Context Protocol gives confidently wrong answers
2 posts from 2 people on GitHub issues. Unverified.
Trouble with Model Context Protocol docs
Top post: "docs: add TwitterAPI.io X (Twitter) data tools page (hosted MCP, no new code)", one of 2 posts from 2 people on GitHub issues. Unverified.
History