Problemsby IbisTrouble with Model Context Protocol reports
LLM apps5 posts from 2 people3d active+00 posts in the last 7 days, 0 the 7 days before (fading)
Posts per day
The posts behind it
5, newest firstfetch: an empty page without Node reports "No more content available" at start_index 0## Problem When Node is not available, readabilipy's pure-Python path returns no content for an empty page, and the server reports "No more content available" for `start_index` 0. That message is meant for paging past the end of a page, not for a simplification failure. With...modelcontextprotocol/servers · cliffhall1 repliesOpen ↗git: an unknown tool called without repo_path reports "'repo_path'" instead of Unknown tool## Problem `call_tool` reads `arguments["repo_path"]` before dispatching on the tool name, so an unknown tool called without `repo_path` fails with the `KeyError` repr `'repo_path'` instead of an "Unknown tool" error. ## Where it is pinned `src/git/tests/test_protocol.py`:...modelcontextprotocol/servers · cliffhall1 repliesOpen ↗git: git_create_branch reports "Created branch" for a branch that already exists at the base## Problem When a branch with the requested name already exists and already points at the base commit, `git_create_branch` reports "Created branch …" although nothing was created. ## Where it is pinned `src/git/tests/test_protocol.py`:...modelcontextprotocol/servers · cliffhall1 repliesOpen ↗git_add reports 'Files staged successfully' when nothing was staged### Describe the bug `git_add` returns the constant string `Files staged successfully` regardless of what the index actually took. `src/git/src/mcp_server_git/server.py:132-153`: `git add` exits 0 when it stages nothing, so two calls report success having done nothing: - `files:...modelcontextprotocol/servers · ConnorMoss022 repliesOpen ↗git_commit reports success and creates an empty commit when nothing is staged### Describe the bug `git_commit` reports success when nothing is staged. It creates an empty commit and returns a hash, so a caller cannot tell it apart from a real commit. `src/git/src/mcp_server_git/server.py:128-130`: `repo.index.commit()` writes a tree from the index...modelcontextprotocol/servers · ConnorMoss021 repliesOpen ↗
Companies and products named
About this problem
Evidence
5 posts from 2 people in 1 place, about 1 a week over 30 days. Mostly on modelcontextprotocol/servers.
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 "reports". First post Sep 5, 2026, latest Oct 4, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other Model Context Protocol problems
Model Context Protocol tables suffer from small files and skewModel Context Protocol users keep filing bugsModel Context Protocol upgrades break working setupsTrouble with Model Context Protocol serverModel Context Protocol rate limits and usage caps block workModel Context Protocol fails to return valid structured outputModel Context Protocol vulnerabilities are hard to triage and patchTrouble with Model Context Protocol sessionTrouble with Model Context Protocol clientModel Context Protocol login, SSO or OAuth breaksModel Context Protocol compute costs spiral out of controlModel Context Protocol gives confidently wrong answers
History
rising to fading
Trouble with Model Context Protocol reports (5 posts)