# Pitfall Log / 踩坑日志

项目：mcp-use/mcp-use

摘要：发现 29 个潜在踩坑项，其中 4 个为 high/blocking；最高优先级：安装坑 - 来源证据：Confusing Logs for empty `resources/` folder。

## 1. 安装坑 · 来源证据：Confusing Logs for empty `resources/` folder

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Confusing Logs for empty `resources/` folder
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1727 | 来源类型 github_issue 暴露的待验证使用条件。

## 2. 安装坑 · 来源证据：Refactor: adaptor deduplicate across MCP adapters

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Refactor: adaptor deduplicate across MCP adapters
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1726 | 来源类型 github_issue 暴露的待验证使用条件。

## 3. 配置坑 · 来源证据：Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works…

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works with enableJsonResponse)
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1724 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 4. 安全/权限坑 · 来源证据：Refactor HttpConnector and StdioConnector with per-connector configuration

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Refactor HttpConnector and StdioConnector with per-connector configuration
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/mcp-use/mcp-use/issues/947 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 5. 安装坑 · 失败模式：installation: Example: Chart Library MCP for financial pattern analysis

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: Example: Chart Library MCP for financial pattern analysis
- 对用户的影响：Developers may fail before the first successful local run: Example: Chart Library MCP for financial pattern analysis
- 证据：failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1286 | Example: Chart Library MCP for financial pattern analysis

## 6. 安装坑 · 来源证据：Example: Chart Library MCP for financial pattern analysis

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Example: Chart Library MCP for financial pattern analysis
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1286 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 7. 配置坑 · 可能修改宿主 AI 配置

- 严重度：medium
- 证据强度：source_linked
- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- 证据：capability.host_targets | github_repo:956472076 | https://github.com/mcp-use/mcp-use | host_targets=mcp_host, claude_code, claude, chatgpt, cursor

## 8. 配置坑 · 失败模式：configuration: @mcp-use/cli 3.5.0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: @mcp-use/cli 3.5.0
- 对用户的影响：Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.0
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.0 | @mcp-use/cli 3.5.0

## 9. 配置坑 · 失败模式：configuration: Refactor HttpConnector and StdioConnector with per-connector configuration

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Refactor HttpConnector and StdioConnector with per-connector configuration
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Refactor HttpConnector and StdioConnector with per-connector configuration
- 证据：failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/947 | Refactor HttpConnector and StdioConnector with per-connector configuration

## 10. 配置坑 · 失败模式：configuration: mcp-use 1.32.0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: mcp-use 1.32.0
- 对用户的影响：Upgrade or migration may change expected behavior: mcp-use 1.32.0
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.0 | mcp-use 1.32.0

## 11. 配置坑 · 失败模式：configuration: mcp-use 1.32.1-canary.2

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: mcp-use 1.32.1-canary.2
- 对用户的影响：Upgrade or migration may change expected behavior: mcp-use 1.32.1-canary.2
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.1-canary.2 | mcp-use 1.32.1-canary.2

## 12. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | github_repo:956472076 | https://github.com/mcp-use/mcp-use | README/documentation is current enough for a first validation pass.

## 13. 运行坑 · 来源证据：fix(cli): send unsubscribe on Ctrl+C in resources subscribe

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：fix(cli): send unsubscribe on Ctrl+C in resources subscribe
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1723 | 来源类型 github_issue 暴露的待验证使用条件。

## 14. 维护坑 · 失败模式：migration: Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SS...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works with enableJsonResponse)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works with enableJsonResponse)
- 证据：failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1724 | Stateful StreamableHTTP transport hangs in mcp-use dev — tool result never reaches client (SSE response dropped, works with enableJsonResponse)

## 15. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | github_repo:956472076 | https://github.com/mcp-use/mcp-use | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | github_repo:956472076 | https://github.com/mcp-use/mcp-use | no_demo; severity=medium

## 17. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | github_repo:956472076 | https://github.com/mcp-use/mcp-use | no_demo; severity=medium

## 18. 能力坑 · 失败模式：capability: Confusing Logs for empty `resources/` folder

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Confusing Logs for empty `resources/` folder
- 对用户的影响：Developers may hit a documented source-backed failure mode: Confusing Logs for empty `resources/` folder
- 证据：failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1727 | Confusing Logs for empty `resources/` folder

## 19. 能力坑 · 失败模式：capability: Refactor: adaptor deduplicate across MCP adapters

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Refactor: adaptor deduplicate across MCP adapters
- 对用户的影响：Developers may hit a documented source-backed failure mode: Refactor: adaptor deduplicate across MCP adapters
- 证据：failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1726 | Refactor: adaptor deduplicate across MCP adapters

## 20. 能力坑 · 失败模式：capability: fix(cli): send unsubscribe on Ctrl+C in resources subscribe

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: fix(cli): send unsubscribe on Ctrl+C in resources subscribe
- 对用户的影响：Developers may hit a documented source-backed failure mode: fix(cli): send unsubscribe on Ctrl+C in resources subscribe
- 证据：failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1723 | fix(cli): send unsubscribe on Ctrl+C in resources subscribe

## 21. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | github_repo:956472076 | https://github.com/mcp-use/mcp-use | issue_or_pr_quality=unknown

## 22. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | github_repo:956472076 | https://github.com/mcp-use/mcp-use | release_recency=unknown

## 23. 维护坑 · 失败模式：maintenance: @mcp-use/cli 3.5.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: @mcp-use/cli 3.5.1
- 对用户的影响：Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.1
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.1 | @mcp-use/cli 3.5.1

## 24. 维护坑 · 失败模式：maintenance: @mcp-use/cli 3.5.2-canary.2

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: @mcp-use/cli 3.5.2-canary.2
- 对用户的影响：Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.2-canary.2
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.2-canary.2 | @mcp-use/cli 3.5.2-canary.2

## 25. 维护坑 · 失败模式：maintenance: @mcp-use/inspector 10.0.0

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: @mcp-use/inspector 10.0.0
- 对用户的影响：Upgrade or migration may change expected behavior: @mcp-use/inspector 10.0.0
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/inspector%4010.0.0 | @mcp-use/inspector 10.0.0

## 26. 维护坑 · 失败模式：maintenance: @mcp-use/inspector 10.0.1-canary.2

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: @mcp-use/inspector 10.0.1-canary.2
- 对用户的影响：Upgrade or migration may change expected behavior: @mcp-use/inspector 10.0.1-canary.2
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/inspector%4010.0.1-canary.2 | @mcp-use/inspector 10.0.1-canary.2

## 27. 维护坑 · 失败模式：maintenance: @mcp-use/inspector 9.0.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: @mcp-use/inspector 9.0.1
- 对用户的影响：Upgrade or migration may change expected behavior: @mcp-use/inspector 9.0.1
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/inspector%409.0.1 | @mcp-use/inspector 9.0.1

## 28. 维护坑 · 失败模式：maintenance: mcp-use 1.31.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: mcp-use 1.31.1
- 对用户的影响：Upgrade or migration may change expected behavior: mcp-use 1.31.1
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.31.1 | mcp-use 1.31.1

## 29. 维护坑 · 失败模式：maintenance: mcp-use 1.32.1-canary.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: mcp-use 1.32.1-canary.1
- 对用户的影响：Upgrade or migration may change expected behavior: mcp-use 1.32.1-canary.1
- 证据：failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.1-canary.1 | mcp-use 1.32.1-canary.1