fix(mcp): two SDK-default list methods answer cacheScope "public", and logging/setLevel answers without a logging capability

未关闭
#131 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
api

调研方向

Start with the cache-control middleware in internal/mcp/server.go around lines 924-946, where listRes.CacheScope is set to "private", and compare it with the go-sdk default handlers for prompts/list, resources/templates/list and logging/setLevel. First decide the intended behavior; the issue leaves this open. Done means the behavior is pinned by a wire-oracle scenario, the middleware comments match it, and the mcp-server spec has a delta.

由索引模型根据 Issue 内容生成。

描述

area:mcp bug priority:low spec-needed
What happens
  • go-sdk's default handlers for prompts/list and resources/templates/list answer {"ttlMs":0,"cacheScope":"public", ...: []}. The cache-control middleware in internal/mcp/server.go (:924-946, where it sets listRes.CacheScope = "private") and its comments say that every codegraph response is cacheScope: "private".
  • logging/setLevel answers {}, but initialize advertises no logging capability.

No test or wire-oracle transcript pins either behavior. The mcp-server spec leaves both out on purpose.

What you expected instead
  • The two list methods answer private, like the four methods the middleware corrects, or the middleware comments name the methods it covers.
  • logging/setLevel answers method-not-found, or initialize advertises the logging capability.
Evidence

Probed on main on 2026-10-17 with a stdio session: initialize, then each method in turn.

Acceptance criteria
  • The behavior of prompts/list, resources/templates/list and logging/setLevel is decided, and a wire-oracle scenario pins it.
  • The middleware comments match the behavior.
  • The fix PR adds the requirement to the mcp-server spec through a delta.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

主要语言
Go
星标
0
派生
0
平均合并
7 小时 42 分钟
30 天内合并 PR
111

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

seanb4t/codegraph-go 的其他 Issue

查看 seanb4t/codegraph-go 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。