On the MCP server itself: This is standard MCP, not tuned for the cloud. It implements the spec directly (JSON-RPC 2.0 over streamable HTTP, with initialize/tools/list/tools/calls and protocol version negotiation), and the server has zero cloud-specific branching. Any MCP-compliant client that connects to http://127.0.0.1:
Although I’ll be straight up with you about one thing: The in-app setup screen right now says cloud-code-first. The recommended path is a cloud mcp add command and the configuration examples point to the cloud’s configuration files, as that is the client I use and test every day. So if you’re on a different MCP client, the server works fine, but you’ll translate those setup steps into your client’s own configuration format instead of copy-pasting. Making that flow more customer-neutral is on my list.
One real caveat that’s not about tuning: Cloud Desktop specifically can’t connect, as its connectors go through Anthropic’s servers and can’t reach servers running locally on your machine. Cloud code (CLI) and other clients that speak the standard HTTP transport directly are all fine.
For reference, the server exposes 21 tools covering functions, invocations, errors, anomalies, cold starts, memory write-sizing, cost analysis, log searches, correlations, and error-pattern stuff, so an assistant can actually query your stitched timeline instead of just reading the raw logs.
<a href