> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staging.alpic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Registry

> Publish your MCP server to the official MCP Registry

Alpic allows you to publish your MCP server directly to the official [MCP Registry](https://registry.modelcontextprotocol.io/). 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](https://github.com/mcp), [Pulse MCP](https://www.pulsemcp.com/) and more.
* **Standardization:** Your server gets a valid `server.json`, ensuring compatibility across MCP clients.

<Tip>
  Published servers follow the MCP Registry [server.json
  schema](https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json). Alpic automatically generates
  and maintains this file for you.
</Tip>

## Publishing Your Server

<Steps>
  <Step title="Navigate to Publishing">
    In your Alpic dashboard, go to your Project and click on the **Publishing** tab.
  </Step>

  <Step title="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
  </Step>

  <Step title="Click New Version">Click the **New Version** button to open the publishing dialog.</Step>

  <Step title="Fill in Server Details">
    Complete the required fields for your server:

    | Field           | Required | Description                                                                      |
    | --------------- | -------- | -------------------------------------------------------------------------------- |
    | **Title**       | Yes      | A human-readable name for your server (max 100 characters)                       |
    | **Description** | Yes      | A brief description of what your server does (max 100 characters)                |
    | **Website URL** | No       | Link to your server's documentation or homepage                                  |
    | **Icon URL**    | No       | URL to a 200×200 pixel icon image for your server (png format)                   |
    | **Headers**     | No       | The specific headers required by your MCP server, often used for authentication. |

    <Accordion title="Configuring Headers" icon="key" open>
      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
    </Accordion>
  </Step>

  <Step title="Preview and Publish">
    Review the JSON preview showing your server.json file, then click **Publish** to submit your server to the registry.
  </Step>

  <Step title="Check the Registry">
    Once published, your server will be available on the [MCP Registry](https://registry.modelcontextprotocol.io/). You can click "View on MCP Registry →" to see your server listed there.
  </Step>
</Steps>

<Warning>Registry publishing is only available for the **Production** environment of your project.</Warning>

## 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](https://semver.org/) (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.

<Note>
  Only semantic versioning is supported. If your existing server.json has a non-semver version, you'll need to update it
  before publishing.
</Note>

### Publishing with a Custom Domain

If you have [custom domains](/distribution/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

<Card title="Distribute Your MCP Server" icon="share-nodes" href="/distribution/publishing">
  Learn about other distribution options beyond the MCP Registry.
</Card>