Skip to content

Conversation

@LaelLuo
Copy link

@LaelLuo LaelLuo commented Sep 16, 2025

Overview

  • Upgrade mcp-go to v0.39.1 which adds server-side handling for logging/setLevel and session logging support
  • Restore server.WithLogging() during initialization so clients can set log level
  • Adapt tool handlers to the new mcp.CallToolRequest API (GetString, GetInt, GetArguments) to keep compatibility with mcp-go >= v0.39

Why
Fixes #79: Previously the server declared logging capability but did not implement logging/setLevel. With mcp-go v0.39.1, the server now implements logging/setLevel (handleSetLevel), and stdio sessions implement SessionWithLogging.

Notes

  • Verified go build ./... succeeds
  • Root go test passes (integration tests require external language servers and are unaffected by this change)
  • No behavior changes to existing tools other than argument accessors updated to the new API

Potential Impact

  • Dependency bump to mcp-go v0.39.1
  • If downstream code accesses request.Params.Arguments directly, it should use helper accessors from the updated API.

…l args adaptation

- Upgrade mcp-go to v0.39.1 which adds server-side handling for `logging/setLevel` and session logging support
- Restore `server.WithLogging()` in initialization so clients can set logging level
- Adapt tool handlers to new `mcp.CallToolRequest` API using `GetString/GetInt/GetArguments()` instead of indexing `Params.Arguments`
- Build succeeds; root `go test` passes; integration tests depend on external LSPs and are unaffected by this fix

Fixes isaacphi#79
@LaelLuo LaelLuo force-pushed the fix/logging-setlevel branch from cf35e89 to c8bdbf2 Compare September 16, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Server declares logging capability but doesn't implement method: "logging/setLevel"

1 participant