Problemsby IbisModel Context Protocol lock-in makes switching costly
Cloud and tool cost2 posts from 2 people2d active+00 posts in the last 7 days, 1 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest first[URGENT / BLOCKING] Unify Local Agent, Session Persistence, Worktrees, and MCP Infrastructure Across Chat and Agents Window...consistently behave like parts of one coherent product. The result is a fragmented and unreliable development workflow. Sessions can disappear after restarting VS Code, the Local harness cannot be used with the same capabilities across both surfaces, Worktree-based isolation is...microsoft/vscode · arin85133 reactionsOpen ↗[BUG] `StaticToolFilter(allowed_tool_names=[])` allows all MCP tools instead of blocking all### Description Passing an explicit empty list `allowed_tool_names=[]` to `StaticToolFilter` or `create_static_tool_filter` allows every non-blocked MCP tool instead of blocking all tools. In `StaticToolFilter.__init__` (`lib/crewai/src/crewai/mcp/filters.py`),...crewAIInc/crewAI · truecallerabrehamOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 2 places, about 1 a week over 14 days. Mostly on crewAIInc/crewAI, microsoft/vscode. Tools named alongside: VS Code.
Frustration Frustration 3 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "vendor-lock" rule about Model Context Protocol. First post Sep 26, 2026, latest Oct 9, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Vendor lock-in makes switching tools costlyGitHub lock-in makes switching costlyKubernetes lock-in makes switching costlyClaude Code lock-in makes switching costlyClaude lock-in makes switching costlyNVIDIA lock-in makes switching costlyllama.cpp lock-in makes switching costlyCodex lock-in makes switching costlyAnthropic lock-in makes switching costlypandas lock-in makes switching costlyApache Airflow lock-in makes switching costlyvLLM lock-in makes switching costly
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 sessionTrouble with Model Context Protocol clientModel Context Protocol login, SSO or OAuth breaksModel Context Protocol compute costs spiral out of control
History
steady to fading
Model Context Protocol lock-in makes switching costly (2 posts)