Problemsby IbisTrouble with Model Context Protocol client
LLM apps3 posts from 2 people2d active+00 posts in the last 7 days, 0 the 7 days before (fading)
Posts per day
The posts behind it
3, newest firsteverything: trigger-elicitation-request is listed for a client that supports only URL-mode elicitation## Problem `trigger-elicitation-request` sends a form-mode elicitation, but it is registered whenever the client declares the `elicitation` capability at all. A client that declares only URL-mode elicitation sees the tool listed, and every call to it fails. ## Where it is pinned...modelcontextprotocol/servers · cliffhall1 repliesOpen ↗git: flag-injection guard messages reach the client wrapped as "Ref ... did not resolve to an object"## Problem The flag-injection guards raise `BadName`, so their own message reaches the client wrapped in GitPython's `Ref ' ' did not resolve to an object`. The rejection works; the message is garbled. ## Where it is pinned `src/git/tests/test_protocol.py`:...modelcontextprotocol/servers · cliffhall1 repliesOpen ↗bug(mcp): MCP OAuth fails to obtain refresh_token and drops client_secret during background token refresh### What happened? When configuring and using remote MCP servers that utilize OAuth 2.0 with Google endpoints (such as Google Workspace APIs like Docs, Sheets, Slides, Drive) or other confidential OAuth providers requiring a `client_secret` for token refresh: 1. **No Refresh...google-gemini/gemini-cli · arsenyspb2 repliesOpen ↗
Companies and products named
About this problem
Evidence
3 posts from 2 people in 2 places, about 3 a week over 5 days. Mostly on modelcontextprotocol/servers, google-gemini/gemini-cli. Tools named alongside: Google Cloud, Gemini.
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 "client". First post Sep 30, 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 outputTrouble with Model Context Protocol reportsModel Context Protocol vulnerabilities are hard to triage and patchTrouble with Model Context Protocol sessionModel Context Protocol login, SSO or OAuth breaksModel Context Protocol compute costs spiral out of controlModel Context Protocol gives confidently wrong answers
History
steady to fading
Trouble with Model Context Protocol client (3 posts)