Changelog

What’s new in MCPCloud

Everything that has reached MCPCloud in production, newest first, on the day it went live. Inside the app, What’s new at the foot of the sidebar shows the same, and mcp changelog prints it in your terminal.

Follow it with the Atom feed

  • This changelog: read it at mcpcloud.sh/changelog, follow the Atom feed, open What’s new at the foot of the app’s sidebar, or run mcp changelog.
  • Read-only tools state every hint outright — not destructive, safe to repeat — as OpenAI’s app review requires. Your server picks this up on its next regenerate and deploy.

  • When an agent such as Cursor asks to connect and its sign-in returns to its own website, the consent page shows its logo and name instead of an initial.

  • Deploying a server no longer disconnects the apps using it: claude.ai, Claude Code and other clients keep working through a redeploy, with no reconnect and no second sign-in to the upstream. Takes effect from the deploy after your server is on runtime 0.19.1.
  • Signing in to an upstream from an agent’s link ends on a page that says you’re connected, instead of “not found”.
  • Give tools human titles with x-mcp-title in your spec, mcp tools edit --title, or Tools ▸ Title & hints.
  • DELETE operations are marked destructive, so clients ask before running them; declare other overwrites destructive with x-mcp-annotations or mcp tools edit --destructive.
  • Mark a server closed-world (mcp servers update --closed-world on or Settings ▸ Closed world) when its tools only act inside the user’s own account.
  • An upstream 403 now leads with the upstream’s own reason instead of telling the user to reconnect.
  • Your customers can run Code Mode, limited to the tools you’ve allowed them.
  • New opt-in setting, Refresh connected clients, which makes already-connected clients start a new session after a deploy that changes your tools.

  • The connections hub: customers see every app they’ve connected across MCPCloud publishers with one verified email, and can disconnect any of them.
  • Tell your upstream API which agent is calling: turn on client identity forwarding and requests carry X-MCP-Client-Name, so your app can show Claude, Cursor or Codex by name.

  • The connect page shows a customer’s real email instead of a generated id.
  • Code Mode passes upstream sign-in links back to the client, so a script that needs a sign-in tells the user where to go.

  • Choose how customers sign in from one place on the End users tab: an MCPCloud account, your sign-in page, your OAuth provider, or federation. The API and CLI (mcp servers end-user sign-in) set the same.
  • Set up your OAuth provider on a page of its own, including providers that only return an OpenID id_token.

  • Point a server at a different spec URL with mcp servers update --source-url or Settings ▸ Spec source; a dry run shows what would change first.
  • Leave an operation out of your server by marking it x-mcp: false in the spec.

  • Rename or delete a tool in place with mcp tools rename and mcp tools delete; access rules follow the tool.
  • CLI --json output piped into another program arrives whole.
  • Code Mode works with clients on the 2026-07-28 MCP protocol.

  • A publisher’s customers can connect with an email code or Google without creating an MCPCloud account.
  • A ci-build API key can run the whole CI sequence, from regenerate to deploy.

  • Server environments: run separate lanes of a server, each with its own config and credentials.

  • Federated servers can send signed-out customers to the publisher’s own sign-in page, and disconnecting cuts off upstream access straight away.

  • Customers can connect an upstream account with OAuth right on the connect page.
  • The connect page keeps your brand colour readable in light and dark, and the end-user tool list has select all.

  • The connect page shows your custom domain as the endpoint and gives copy-ready setup snippets for each client.
  • Install a skill by its marketplace id with mcp skills install.

  • The End users tab shows how your customers use your server.

  • Transfer a server or a skill to another organization, from the dashboard or with mcp servers transfer and mcp skills transfer; a live server is redeployed under its new owner.
  • A ci-build API key preset for CI pipelines.

  • Spec drift shows a readable diff of what changed upstream.

  • MCP servers speak the 2026-07-28 protocol alongside the 2025 one, so newer clients connect without anything changing for existing ones.
  • Spend caps count over exact rolling windows.