Skip to content
Problems.

Model Context Protocol upgrades break working setups

Outages and change4 posts from 3 people3d active+11 post in the last 7 days, 1 the 7 days before (steady)

Posts per day

Posts per day4 posts, Sep 8 to Sep 25

The posts behind it

4, newest first
PostDate
server-memory: saveGraph rewrites memory.jsonl via temp-file + rename, dropping an existing file's permission bits (0600 -> 0644) and silently overwriting read-only files**server-memory: `saveGraph` rewrites `memory.jsonl` through a temp file + rename, so an existing file's permission bits are silently dropped (0600 -> 0644) and read-only files are silently overwritten** ### Environment - Package: `@modelcontextprotocol/server-memory`...modelcontextprotocol/serversBlueX888Sep 196 days ago
git_checkout reports "Switched to branch 'X'" when the checkout actually detached HEAD### What happens `git_checkout` validates `branch_name` with `repo.rev_parse(...)`, which resolves any revision - a commit sha, a tag, `HEAD~1`, a remote-tracking ref - not only branch names. It then checks out and returns a fixed string: `src/git/src/mcp_server_git/server.py`...modelcontextprotocol/serversbuyan201430-codeSep 1411 days ago
[Bug]: McpToolSpec.allowed_tools unintentionally filters MCP resources when include_resources=True### Bug Description `McpToolSpec.allowed_tools` is documented as a filter for **tools**, but `fetch_resources()` currently reuses the same list to filter MCP resources and resource templates. That means a caller who intentionally restricts callable tools while enabling resources...run-llama/llama_indexanupamking01Sep 82 weeks ago
[Bug]: MCP tool_call_logs_callback can receive empty logs when application logging is already configured### Bug Description `BasicMCPClient._configure_tool_call_logs_callback()` currently relies on `logging.basicConfig(..., handlers=[stream_handler])` to attach a temporary `StringIO` handler before an MCP tool call. `logging.basicConfig()` is intentionally a no-op once the root...run-llama/llama_indexanupamking01Sep 82 weeks ago

Companies and products named

Company or productPosts naming it
Model Context Protocol4
LlamaIndex2
Jupyter1
About this problem

Evidence

4 posts from 3 people in 2 places, about 2 a week over 12 days. Mostly on run-llama/llama_index, modelcontextprotocol/servers. Tools named alongside: LlamaIndex, Jupyter.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "breaking-changes" rule about Model Context Protocol. First post Sep 8, 2026, latest Sep 19, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

History

  • 2026-09-25 Corroboration: unverified to corroborated
  • 2026-09-25 Momentum: fading to steady
  • 2026-09-25 Added: Model Context Protocol upgrades break working setups (2 posts)

Rising problems by email

Mondays: the problems in data, tech and AI that grew fastest that week.

Double opt-in. Unsubscribe any time.