docs: Add Runpod MCP server updates to June 2026 release notes#708
docs: Add Runpod MCP server updates to June 2026 release notes#708promptless[bot] wants to merge 1 commit into
Conversation
| @@ -31,10 +31,22 @@ description: "New features, fixes, and improvements for the Runpod platform." | |||
|
|
|||
| You can now request a GPU that's currently out of capacity and get notified by email when it becomes available. Runpod saves your pod configuration so you can deploy immediately when capacity returns. | |||
There was a problem hiding this comment.
The "Sign in with Runpod" entry is based on PR #27, which added the hosted Streamable HTTP transport and the OAuth "Sign in with Runpod" flow (stateless token passthrough, no API key stored on disk) while leaving the existing local stdio + API key mode unchanged. This shipped in @runpod/mcp-server@1.3.0 (npm publish 2026-06-18), placing it in the June 2026 section.
Source: runpod/runpod-mcp#27
|
|
||
| <h4><Badge color="green">New Release</Badge> Sign in with Runpod for the MCP server</h4> | ||
|
|
||
| You can now connect AI coding agents to a hosted [Runpod MCP server](/get-started/mcp-servers) over HTTP and authenticate with the "Sign in with Runpod" OAuth flow, so you no longer need to store a Runpod API key on disk. Local connections that use an API key continue to work as before. |
There was a problem hiding this comment.
The "Expanded MCP server tools and REST API v2" entry draws on the @runpod/mcp-server@2.0.0 release (PR #50 changeset): defaulting REST to v2 (v2-rest.runpod.io/v2), the create-endpoint move from the v1 templateId model to the v2 inline-config imageName + gpuPoolIds model with RUNPOD_REST_VERSION=v1 as the opt-out, and the v2-only tags/billing/endpoint-workers/catalog tools. Serverless job tools and GPU/data-center discovery come from the earlier 1.2.0 release (npm publish 2026-06-05); 2.0.0 published 2026-06-29.
Source: runpod/runpod-mcp#50
|
|
||
| <h4><Badge color="blue">Improvement</Badge> Hub navigation consolidated</h4> | ||
|
|
||
| Hub navigation items are now consolidated into a single unified entry, making it easier to find templates and repos. |
There was a problem hiding this comment.
The "Guided install command" entry is based on the @runpod/mcp-server@1.4.0 changeset in PR #33, which added the npx @runpod/mcp-server@latest add wizard that detects installed agents (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code) and writes MCP config for each selected one, with remove to undo. Published to npm 2026-06-26, so it belongs in the June 2026 section.
Source: runpod/runpod-mcp#33
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.) |
Open this suggestion in Promptless to view citations and reasoning process
Adds three release-notes entries to the June 2026 section of the product updates page covering shipped Runpod MCP server changes: hosted HTTP transport with the "Sign in with Runpod" OAuth flow (v1.3.0), expanded tool coverage plus the default switch to REST API v2 with the create-endpoint breaking change (v1.2.0/v2.0.0), and the guided
npx @runpod/mcp-server addinstall command (v1.4.0). Scoped to changes published to npm in June 2026; unreleased log streaming (PR #52) is excluded.Trigger Events
Tip: Leave inline comments with
@Promptlesson suggestion diffs in the Promptless dashboard for targeted refinements 💬