@runpod/mcp-server 4.4.0 → 4.5.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # @runpod/mcp-server
 
+## 4.5.0
+
+### Minor Changes
+
+- 83bffb7: Hosted server: a new optional ALP tool, `report_how_user_found_runpod`, asks
+  the agent once per account how its user ended up on Runpod: the kind of
+  work (`useCase`) and why Runpod came up (`source`: `searched`,
+  `user_named`, `recommended`, `other`), or that it has no such context
+  (`noContext`). It collects categories and at most a short generic note,
+  never the user's own words. The ask rides in the `initialize` instructions; on each
+  `initialize` with a resolved account the server checks the storage sink and
+  omits the ask once the account has answered (a failed lookup keeps the ask),
+  and the sink keeps the first answer per account, with the server answering
+  `already_submitted` to any later one. Answers are stored with the
+  other ALP submissions under their own `referral` route, with the note capped at 200
+  characters, and scrubbed like every other submission. Absent on local stdio
+  and whenever the sink is not configured, like the other ALP tools.
+- ff02fdb: Every tool now carries a human-readable `title` in tools/list (for example `List GPU types` for `list-gpu-types`), so hosts can show readable names and the server meets directory review requirements. Generated tools derive the title from their name, with overrides in `specgen/generator-config.yaml`; curated tools declare their own.
+
+### Patch Changes
+
+- da524df: GraphQL errors that Runpod returns on an HTTP 200 now fail the tool call with a status taken from the error code (401, 403, 400 including Runpod's own `RUNPOD` input errors, otherwise 502) instead of 200, so agents get the matching recovery hint. A non-array `errors` field no longer crashes the call.
+- d075b00: Network failures reaching the Runpod API (DNS, connection refused, unreachable host, TLS errors, or a connection dropped mid-request) now come back as tool errors with the underlying `cause` code and a recovery hint, instead of escaping as an opaque JSON-RPC `-32603 fetch failed`. Failures where the request never reached Runpod say a retry is safe; a dropped connection says a write may have been applied and to check with a get- or list- tool before calling again.
+- 6a577ea: Update `@runpod/plugin-knowledge` from 1.7.4 to 1.8.0, so `list-guides` and `read-guide` serve the plugin's 1.8.0 skills and guides, including the new `runpod-build-template` skill.
+
 ## 4.4.0
 
 ### Minor Changes