Cloudsmith MCP

An artifact registry is exactly the kind of system where an agent is useful and where a careless write is expensive. Cloudsmith ships its MCP server inside the Cloudsmith CLI rather than as a separate service, and the design reflects that tension: broad read access, and the genuinely consequential operations disabled unless you turn them on.

Setup

The server needs the Cloudsmith CLI (Python 3.10+). Auto-configuration writes the client config for you:

cloudsmith mcp configure
cloudsmith mcp configure -P my-profile   # a specific profile

Claude Desktop, Cursor, VS Code (Copilot) and Gemini CLI are supported for automated setup; any other client can be pointed at cloudsmith mcp start manually.

Authentication

It reuses your existing CLI credentials, so there is no second secret to manage. API keys already configured are picked up automatically. SSO users must run `cloudsmith auth` before starting the server — an MCP client cannot trigger the SSO flow once the server is running, so an unauthenticated start simply fails later.

Tools, and what is switched off

Tools are generated dynamically from Cloudsmith's OpenAPI specification, so coverage tracks the platform's API rather than a hand-maintained list. Enumerate what is available with:

cloudsmith mcp list_tools -a
cloudsmith mcp list_groups -a

Disabled by default: package uploads and validation, webhooks, signing keys, upstream settings, broadcasts, rates, and several administrative groups. Re-enable per tool or per group in ~/.cloudsmith/config.ini:

[default]
mcp_allowed_tools=workspaces_policies_simulate_list
mcp_allowed_tool_groups=metrics

That allowlist model is the main reason to prefer this over a generic API wrapper — the blast radius is a config decision you make deliberately, not a default you inherit.

Useful for asking where a vulnerable package version is still being consumed, auditing repository and policy configuration, and pulling usage metrics without leaving the assistant.