bitdrift’s Snow Pettersen wrote up why the company added a remote MCP server after shipping a public API, a bd CLI and agent skills, and the reason is not the one usually given. Token cost was the old objection to MCP, and tool search plus code mode have narrowed it. What decided it was auth. A CLI in an ephemeral cloud sandbox has to re-authenticate every session, and the token disappears when the VM rotates. With MCP, “the authentication context is lifted out of the session and handled by the harness.” bitdrift supports both Client ID Metadata Documents, now the recommended registration path, and Dynamic Client Registration for clients that have not moved over.
The engineering detail is the valuable part and none of it is a marketing number. Tools are generated from annotations on the same Protobuf definitions that produce the public API and the CLI, including read-only, destructive and idempotent hints, so one set of protos feeds both front doors. The 2026-07-28 stateless spec let them mount MCP routes on the existing API server, one tool call to one RPC. And the hardest lesson is about size: exported as-is, the Workflow API’s create schema came to 32k tokens. So tools grew options for asking for less, field selection on logs and spans and summary data instead of full chart series, which they note makes the MCP surface feel more like GraphQL. “For an agent, asking for less is the whole point.”
The bitdrift record agrees with the architecture the post describes: a schema-first protobuf API over gRPC, Connect and gRPC-over-JSON, operated through a web portal and the bd CLI, catalogued as the single bitdrift Public API page. That page is the thing the post says both the CLI and the MCP server are re-exports of, which is why it is one page and not three.
The Kin Score is 58.6, strong, carried by access clarity (81.6) and developer ergonomics (78.6), with contract governance at 18.2. Agent Readiness is 26.3, agent-aware: agent skills, auth clarity, error semantics and the event surface are lit. Unlit are mcp_server, dynamic_client_registration, protected_resource_metadata and idempotency, every one of which this post says bitdrift now ships, and the last of which is literally an annotation on each tool. The record was scored on 2026-11-06, nine days after the post; the probes have not found mcp.bitdrift.io. That is the next rescore’s job, and the gap between what bitdrift built and what an outside agent can find is the measurement worth watching.