For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Add your MCP server to the Solo Enterprise for agentregistry catalog so that you can start deploying the MCP server to connected runtimes.

About the registry catalog

Solo Enterprise for agentregistry serves as a catalog for your AI artifacts, including agents, skills, and MCP servers. You can decide which agents you want to make available to your registry users by adding them to the registry catalog. After an agent is published in the catalog, registry users can deploy them to a connected runtime.

Before you can add an MCP server to the catalog, you must either build a Docker container image and push it to your container image registry or store the server’s source code in a GitHub repository. The method that you need to use depends on the type of runtime that you plan to deploy your MCP server to.

Before you begin

1. Set up an OIDC provider so that users can authenticate with the registry.

2. Install Solo Enterprise for agentregistry and the arctl CLI.

3. Port-forward the Solo Enterprise for agentregistry server on port 12121 if you have not done so already. The registry is not exposed externally by default, so you need port-forwarding to reach it from your local machine.

   kubectl -n agentregistry-system port-forward svc/agentregistry-enterprise-server 12121:12121

4. Create an MCP server.
5. Build the Docker image or store the source code.

Publish the server

1. Update the mcp.yaml file with the GitHub or GitLab repository where the MCP server source code is stored. By default, the scaffold only includes the image location and does not add a repository URL. If the repository is private, configure your credentials first, then set credentialsRef on the repository. The example in this guide uses the https://github.com/solo-io/doc-examples sample repository. Optionally, update the URL to use your own GitHub repository instead.

   cat > mymcp/mcp.yaml <<EOF
   apiVersion: ar.dev/v1alpha1
   kind: MCPServer
   metadata:
     name: mymcp
   spec:
     description: mymcp MCP server
     source:
       package:
         launch:
           args:
           - type: positional
             value: src/main.py
           - type: positional
             value: --transport
           - type: positional
             value: http
           - type: positional
             value: --host
           - type: positional
             value: 0.0.0.0
           - type: positional
             value: --port
           - type: positional
             value: "3000"
           command: python3
         origin:
           identifier: localhost:5001/mymcp:latest
           oci:
             serverName: mymcp
           type: oci
         transport:
           path: /mcp
           port: 3000
           type: http
       repository:
         url: https://github.com/solo-io/doc-examples
         subfolder: agentregistry/mymcp
     title: mymcp
   EOF

2. Publish the MCP server to the Solo Enterprise for agentregistry catalog.

   arctl apply -f mymcp/mcp.yaml

   Example output:

   ✓ MCPServer/mymcp created
   

3. Verify that the MCP server is published in the catalog.

   arctl get mcp

   Example output:

   NAME    TAG      DESCRIPTION
   mymcp   latest   mymcp MCP server
   

4. Optional: Open the registry UI to review your published MCP server.

   

   

Next

Now that your MCP server is registered in the registry catalog, you can deploy it to one of the supported runtimes.