Anthropic Launches Developer Portal to Package, Submit, and Track Claude Plugins

Anthropic has officially launched a dedicated developer portal that enables builders to package, submit, and track plugins for distribution across the Claude directory. Available to developers on paid tiers, the workflow allows engineers to publish either single remote Model Context Protocol (MCP) connectors or comprehensive plugin bundles hosted on GitHub that combine MCP servers, Agent Skills, commands, hooks, and LSPs for Claude Code. The portal provides end-to-end status tracking through the review pipeline alongside live post-publication usage analytics. The release also integrates MCP 2.0 capabilities, including MCP Apps for embedding interactive chat interfaces and Enterprise Managed Auth for zero-touch OAuth. For DevOps and AI platform engineers, this release addresses the operational friction of distributing and maintaining context-aware toolchains. Rather than requiring internal developers or end users to manually clone repositories, configure local configuration files, and manage environmental variables for each custom MCP server, plugins package complex multi-tool dependencies into unified units. Platform teams gain centralized visibility into review approvals and real-time usage metrics, transforming experimental AI tooling into governed, auditable internal services. This move reinforces the industry shift from basic prompt wrappers and proprietary plug-in formats toward standardized open protocol ecosystems. Following Anthropic's rollout of the Claude Marketplace and expanded MCP adoption across enterprise ecosystems, formalizing the directory submission pipeline mirrors how package managers transformed language runtimes. Establishing MCP as the standard abstraction layer for model-to-infrastructure connectivity allows organizations to avoid vendor lock-in when binding LLMs to internal databases, version control systems, and deployment automation. In practice, engineering organizations building custom automation should audit their internal MCP integrations and prepare bundled repositories targeting the new portal. Teams operating in regulated environments should prioritize Enterprise Managed Auth to ensure third-party and internal tools align with existing IAM boundaries. Furthermore, platform architects should establish continuous integration workflows that test MCP tools against schema revisions before submitting updates, ensuring smooth navigation through the review pipeline while monitoring directory analytics for performance regressions.