Skip to main content
Alpic allows you to publish your MCP server directly to the official MCP Registry. Having your server listed on the registry provides several benefits:
  • Discoverability: Makes it easier for people and AI agents to find your server from a single, authoritative source of the MCP ecosystem.
  • Subregistry distribution: The registry feeds into subregistries like GitHub MCP, Pulse MCP and more.
  • Standardization: Your server gets a valid server.json, ensuring compatibility across MCP clients.
Published servers follow the MCP Registry server.json schema. Alpic automatically generates and maintains this file for you.

​
Publishing Your Server

1

Navigate to Publishing

In your Alpic dashboard, go to your Project and click on the Publishing tab.
2

Review Current Status

The MCP Registry card shows your current publishing status:
  • If you haven’t published yet, you’ll see “No published version yet”
  • If you’ve published before, you’ll see your latest published version with a link to view it on the MCP Registry
3

Click New Version

Click the New Version button to open the publishing dialog.
4

Fill in Server Details

Complete the required fields for your server:
FieldRequiredDescription
TitleYesA human-readable name for your server (max 100 characters)
DescriptionYesA brief description of what your server does (max 100 characters)
Website URLNoLink to your server’s documentation or homepage
Icon URLNoURL to a 200×200 pixel icon image for your server (png format)
HeadersNoThe specific headers required by your MCP server, often used for authentication.
If your server requires additional headers (e.g. API key authentication), you can configure them in the optional fields section. For each header, specify:
  • Name: The HTTP header name (e.g., Authorization, X-API-Key)
  • Description: Explain what this header is for (can be displayed to the user when installing your server from the registry). If you are requiring an API key, you can add the URL to get one here.
  • Required: Whether users must provide this header when installing your server from the registry
  • Secret: Whether the value should be treated as sensitive data
5

Preview and Publish

Review the JSON preview showing your server.json file, then click Publish to submit your server to the registry.
6

Check the Registry

Once published, your server will be available on the MCP Registry. You can click “View on MCP Registry →” to see your server listed there.
Registry publishing is only available for the Production environment of your project.

​
Additional Notes

​
Server Naming Convention

When you publish to the registry, your server is automatically named using the reverse domain notation: 
{reversed-domain}/{project-name}
For example, if your production domain is mcp.example.com and your project is named my-server, the registry name will be: 
com.example.mcp/my-server
This naming convention ensures uniqueness and clear ownership of servers in the registry.

​
Version Management

Alpic uses semantic versioning (semver) for registry publishing. Each time you publish:
  • The version number is automatically incremented (patch version)
  • Your first publication starts at version 0.0.1
  • Subsequent publications increment: 0.0.1 → 0.0.2 → 0.0.3, etc.
Only semantic versioning is supported. If your existing server.json has a non-semver version, you’ll need to update it before publishing.

​
Publishing with a Custom Domain

If you have custom domains configured for your production environment, you can publish your server under any of your verified domains. When you have multiple domains, you’ll see tabs in the Publishing section allowing you to manage registry entries for each domain separately.

​
Next Steps

Distribute Your MCP Server

Learn about other distribution options beyond the MCP Registry.