Cloudsmith launches MCP Server to enhance developers' AI-powered workflows. Cloudsmith, a leading cloud-native artifact management platform, today announced the early access launch of its Model Context Protocol (MCP) Server. This new integration layer brings Cloudsmith's capabilities directly into the developer's AI-powered workflows. Built to connect the AI tools developers already use like Claude or CoPilot directly into the software supply chain, it's helping teams better understand, manage, and make decisions around their artifacts - all within existing workflows. A new phase in ai-led development. The rise of AI-powered development has changed how developers and engineers interact with software artifacts, introducing new ways of working. Developers are increasingly relying on AI agents and LLMs to handle the day-to-day tasks, and as these workflows evolve, the tools that power modern software development must integrate seamlessly with the agents and interfaces developers use today and those they will use in the future. The MCP Server ensures those interactions happen where developers already build, without the need to make API calls, log into separate UIs, or switch between tools. With Cloudsmith's MCP Server, developers can simply ask their AI assistant to inspect a package, review a build, or trigger a workflow in natural language - meeting developers where they work, ensuring the same trusted artifact data and governance are available across every interface. A bridge between AI and the software supply chain. Built on the open Model Context Protocol (MCP) standard, Cloudsmith's implementation connects LLMs directly to Cloudsmith's artifact ecosystem. Through natural language, developers can retrieve and interpret details about their repositories, packages, and builds. They can also initiate secure, non-destructive actions through MCP-mediated API calls with full audit logs to maintain visibility over every interaction. Within defined governance boundaries, each LLM or agent can perform meaningful actions like analyzing usage trends, defining policies through Cloudsmith's policy-as-code engine, or taking approved actions on their repositories, all from within the environments where developers already work. "AI is redefining how developers work, moving from manual clicks to natural language interactions. We see this shift every day with our customers. Cloudsmith's MCP Server is a necessary bridge to this new way of working," said Alison Sickelka, VP of Product at Cloudsmith. "By integrating directly with tools like Claude and CoPilot, we ensure engineers can manage, secure, and make decisions about their software artifacts simply by asking a question within the environment they already use. This isn't just about convenience, it brings trusted artifact data and governance exactly where developers build, making the AI part of the secure software supply chain, not separate from it." AI is transforming software development in several important ways. The first is through tools like the MCP Server, which bring AI directly into developers' everyday workflows. The second is through the emergence of new artifact types and data models that require the same level of management and control as traditional software packages - a challenge Cloudsmith addresses with its ML Model Registry, now generally available. And the third is through the sheer acceleration of software creation itself, driven by AI-assisted development. To support this new reality, Cloudsmith has expanded its Enterprise Policy Manager with enhanced policy enforcement, automation, and real-time visibility features. Together, these innovations form three pillars of a modern, AI-ready software supply chain - one that gives developers the confidence, control, and insight they need to build securely and at scale.

Cloudsmith launches ML Model Registry to provide a single source of truth for AI models and datasets.

Cloudsmith Ltd has reworked the implementation and introduced a dedicated endpoint (helm.oci.cloudsmith.io) which allows users to push and pull Helm charts as OCI artifacts, now correctly identified and displayed as Helm packages.