Update to rmcp 3.1.0
rmcp left beta on 2026-07-28 and reached 3.1.0 on 2026-07-31, so the pin moves off 3.0.0-beta.2. get_info now sets server_info. ServerInfo::default() reports rmcp own crate name and version, so the server was identifying itself as rmcp 3.1.0 rather than weather 1.0.0 as the other three quickstarts do. The hand-written list_tools stays: rmcp-macros 3.1.0 still generates ttl_ms: None, cache_scope: None, which a strict client rejects. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
65d1a92cf8
commit
d6cf28629f
1 changed files with 33 additions and 18 deletions
|
|
@ -7,7 +7,7 @@ edition = "2024"
|
|||
anyhow = "1.0.100"
|
||||
genai = "0.4.2"
|
||||
jsonschema = "0.35"
|
||||
rmcp = { version = "3.0.0-beta.2", features = ["server", "client", "transport-io", "transport-child-process"] }
|
||||
rmcp = { version = "3.1", features = ["server", "client", "transport-io", "transport-child-process"] }
|
||||
tokio = { version = "1.47.1", features = ['full']}
|
||||
tracing = "0.1.41"
|
||||
tracing-subscriber = {version = "0.3", features = ["env-filter"]}
|
||||
|
|
|
|||
Loading…
Reference in a new issue