Data and AI struggles

1,730 problems · 342 companies

Outages and change

Model Context Protocol upgrades break working setups

18 posts from 15 people14d activeSteady, +3 this week

Posts per day

Posts per day18 posts, Sep 8 to Nov 9

The posts behind it

GitHub issuesn8n-io/n8n · clucas-mauginNov 4

MCP SQL tools fail with “only 1 query parameter(s) are set” after upgrading to 2.45.7

...string Comma-separated list of values: $1: schema name $2: table name Example failing MCP tool call: . { "Query_Parameters": "dbo,tbl_Projet" } The same error occurs with: . { "Query_Parameters": "dbo,tb_Activite" } A different tool using keyword and origin parameters also...

4 replies
GitHub issuesmodelcontextprotocol/servers · cliffhallNov 4

filesystem: edit_file's whitespace-tolerant match fails when oldText ends with a newline

## Problem `edit_file`'s tool description (since #5379) states the matching rule: "whole lines match with leading and trailing whitespace ignored". An `oldText` made of whole lines **that ends with a newline** breaks it. When the text differs from the file only in indentation,...

GitHub issuesmodelcontextprotocol/servers · cliffhallNov 4

filesystem: write_file into a missing directory returns a raw chdir error showing the server's working directory

## Problem When the parent directory of a `write_file` target does not exist, the server returns the raw Node error from its pinned-directory write instead of its own "Parent directory does not exist" message (`src/filesystem/lib.ts:550`). That error: - **shows the server...

GitHub issuescrewAIInc/crewAI · RaycarlLeiNov 2

[BUG] MCP tool calls are sent again after a timeout, so one action can run a tool up to 3 times

### Description When an MCP `tools/call` times out or hits a transport error after the request was sent, CrewAI sends the same call again, up to `MCP_MAX_RETRIES` (3) times. The server may already have run the tool, so a slow non-idempotent tool (send an email, create an order,...

2 replies
GitHub issuesmodelcontextprotocol/servers · tonyweckstrom1987Oct 30

memory: add descriptions to the top-level array parameters of create_entities, create_relations, add_observations and delete_observations

...### Alternatives or workarounds you have tried None on the server side. Clients and models currently see only the property names (entities, relations, observations, deletions) for these four parameters. ### Already built it locally? Not built locally. The suggested prompt is in...

2 replies
GitHub issuesBerriAI/litellm · ianleekqOct 24

[Bug]: MCP: a virtual key whose only tool restriction is a deleted MCP toolset can call every tool on the server (a team in the same state is denied)

## What happened A virtual key is limited to one tool by an MCP toolset (`object_permission.mcp_toolsets`). While the toolset exists, the key can call only that tool. After the toolset is deleted, the key's `mcp_toolsets` still names it, and the key can now list and call every...

2 replies
GitHub issuesgoogle-gemini/gemini-cli · Rauneet-coderOct 19

MCP tool discovery ignores nextCursor and silently omits tools after the first page

### What happened? MCP tool discovery ignores `nextCursor` from a `tools/list` response. When a server advertises tools across multiple pages, Gemini CLI discovers only the first page, with no diagnostic that additional tools were omitted. On `main` at...

1 replies
Redditr/aws · u/investigatormakerOct 19

ControlTower: open-source, self-hosted gateway to see, gate and approve what your AI agents send over LLM and MCP calls

...MCP servers in your AWS environment, you've probably been asked a simple question that's hard to answer: where is this agent actually sending data?. Once an agent can call models and tools for itself, the traffic gets hard to follow. Platform and security teams usually want...

GitHub issuesopenai/codex · Ricardo9527Oct 16

Composer input predictions eagerly start MCP servers: please avoid tool initialization or provide a separate switch

## Summary Please stop starting live MCP servers just to generate gray inline composer suggestions, or provide a supported switch that prevents MCP initialization specifically for predictions while keeping MCP available for normal submitted tasks. The suggestion is still draft...

2 reactions2 replies
GitHub issuesmodelcontextprotocol/servers · jw-ondOct 15

everything: add focused annotation-presence registration tests

...Existing MCP tool-annotation metadata and its registration paths. ## Alternatives or workarounds you have tried Relying on the existing wire-level snapshots alone remains a reasonable alternative if maintainers consider the additional registration check redundant. I searched...

GitHub issuesmodelcontextprotocol/servers · cliffhallOct 4

filesystem: edit_file's whitespace-tolerant matcher mangles indentation

## Problem When `edit_file` falls back to its whitespace-tolerant line matcher (`lib.ts`), the replacement loses the file's indentation: when `oldText`'s line has no indent, lines after the first lose theirs, and a replacement line whose `oldText` line has no indent ignores the...

1 replies
GitHub issuesmlflow/mlflow · AmazinghorseliOct 3

[BUG] MCP server version search rewrites quoted name filter values containing versionLIKE/versionILIKE

> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...

1 replies
GitHub issuesmicrosoft/vscode · bsgtgodfreySep 30

Cannot toggle MCP tools from chat, all requests return 502 Cannot have more than 128 tools per request.

Type: Bug After updating to 1.141.0-insider, customendpoint model chat requests are all returning an error "502 Cannot have more than 128 tools per request." Chat requests were succeeding prior to updating with the same model and configured tools. There does not appear to be any...

1 replies
GitHub issuesBerriAI/litellm · seanb4tSep 23

[Bug]: MCP tools/call on a single-server endpoint returns 404 "Tool not found" when a different replica served tools/list (oauth_passthrough servers)

...either. I have not traced why. 4. The upstream never receives the `tools/call` from the failing replica. (Separately, on every call, the proxy also sends the upstream one request without the forwarded `Authorization` header and logs `MCP client run_with_session failed for `....

GitHub issuesmodelcontextprotocol/servers · BlueX888Sep 19

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`...

1 replies
GitHub issuesmodelcontextprotocol/servers · buyan201430-codeSep 14

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`...

1 replies
GitHub issuesrun-llama/llama_index · anupamking01Sep 8

[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...

2 replies
GitHub issuesrun-llama/llama_index · anupamking01Sep 8

[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...

1 replies

Companies and products named

About this problem

Evidence

18 posts from 15 people in 10 places, about 2 a week over 58 days. Mostly on modelcontextprotocol/servers, run-llama/llama_index, BerriAI/litellm. Tools named alongside: GitHub, LlamaIndex, Jupyter, GitHub Copilot.

Frustration Frustration 1 of 3· Seen on GitHub issues, Reddit

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 Nov 4, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

GitHub upgrades break working setups

87 posts from 75 people on GitHub issues, Hacker News, Stack Overflow.

Upgrades and new releases break working setups

76 posts from 62 people on GitHub issues, Reddit, App Store reviews.

Claude Code upgrades break working setups

67 posts from 60 people on GitHub issues, Hacker News, Reddit.

Codex upgrades break working setups

65 posts from 58 people on GitHub issues, Reddit.

DuckDB upgrades break working setups

37 posts from 28 people on GitHub issues.

Claude upgrades break working setups

35 posts from 34 people on GitHub issues, Reddit, Hacker News.

ClickHouse upgrades break working setups

31 posts from 20 people on GitHub issues.

Anthropic upgrades break working setups

27 posts from 22 people on GitHub issues.

PyTorch upgrades break working setups

26 posts from 21 people on GitHub issues, Reddit.

ChatGPT upgrades break working setups

26 posts from 26 people on GitHub issues, Community forums, App Store reviews.

OpenAI upgrades break working setups

25 posts from 25 people on GitHub issues, Reddit, Community forums.

Open WebUI upgrades break working setups

25 posts from 2 people on GitHub issues.

Other Model Context Protocol problems

Model Context Protocol users keep filing bugs

Top post: "issue: Realtime voice unable to invoke MCP tools", one of 55 posts from 23 people on GitHub issues, Reddit.

Model Context Protocol dependency conflicts break installs

6 posts from 4 people on GitHub issues.

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 10 posts from 8 people on GitHub issues.

Model Context Protocol rate limits and usage caps block work

9 posts from 6 people on GitHub issues, Hacker News.

Model Context Protocol vulnerabilities are hard to triage and patch

6 posts from 6 people on Glyph Ibis, GitHub issues.

Model Context Protocol fails to return valid structured output

5 posts from 5 people on GitHub issues, Reddit.

Trouble with Model Context Protocol empty

Top post: "Settings env vars: ${VAR:-default} ignores default when VAR is set but empty", one of 4 posts from 3 people on GitHub issues.

Trouble with Model Context Protocol session

Top post: "docs: correct README MCP examples and distinguish checkpointing from session management", one of 4 posts from 3 people on GitHub issues.

Trouble with Model Context Protocol create

Top post: "memory: create_entities, create_relations and add_observations could declare idempotentHint: true", one of 3 posts from 3 people on GitHub issues.

Model Context Protocol login, SSO or OAuth breaks

3 posts from 3 people on GitHub issues.

Model Context Protocol compute costs spiral out of control

2 posts from 1 person on GitHub issues. Unverified.

History

Momentum went from rising to steady.

Nov 9, 2026

Momentum went from steady to rising.

Nov 7, 2026

Momentum went from rising to steady.

Nov 6, 2026

Momentum went from fading to rising.

Nov 5, 2026

Momentum went from steady to fading.

Oct 31, 2026

Momentum went from fading to steady.

Oct 30, 2026

Momentum went from steady to fading.

Oct 26, 2026

Momentum went from fading to steady.

Oct 17, 2026

Momentum went from steady to fading.

Oct 11, 2026

Momentum went from fading to steady.

Oct 8, 2026

Momentum went from steady to fading.

Oct 7, 2026

Momentum went from fading to steady.

Oct 5, 2026