Model Context Protocol (MCP) publishing

Learn how to publish MCP servers to the official MCP Registry. This section covers authentication, package types, remote servers, versioning, GitHub Actions automation, and moderation policies.

MCP Registry Supported Package Types

This article documents the package types supported by the MCP Registry, including npm, PyPI, NuGet, Docker/OCI images, and MCPB packages. It provides configuration examples for each package type and explains how ownership verification works for publishing MCP servers to the registry.

Publishing remote MCP servers

This article explains how to publish and configure remote MCP servers in the MCP Registry. It covers the remotes property in server.json, transport types, URL template variables for multi-tenant deployments, and HTTP header configuration.

How to Authenticate When Publishing to the Official MCP Registry

The MCP Registry supports different authentication methods like GitHub, DNS, and HTTP authentication. Which authentication method you choose determines the namespace of your server's name.

Versioning Published MCP Servers

This article explains how version strings work for MCP servers published to the MCP Registry. It covers the version format requirements, explains why semantic versioning is recommended, and provides best practices for aligning server versions with package and API versions.

How to automate publishing with GitHub Actions

This guide explains how to set up GitHub Actions to automatically publish your MCP server to the MCP Registry whenever you push a new version tag. It covers creating workflow files, adding secrets, and troubleshooting common issues.

The MCP Registry Moderation Policy

This article outlines the moderation policy for the MCP Registry, a community-supported directory of servers. It explains what types of content are removed from the registry and what is allowed to remain, including the appeals process for incorrect removals.