Publish to catalog
Add your MCP server to the Solo Enterprise for agentregistry catalog so that you can start deploying the MCP server to connected providers.
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 provider.
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 provider that you plan to deploy your MCP server to.
| Deployment target | Example provider | Docker image vs. GitHub repo |
|---|---|---|
| AI runtimes in Kubernetes | Solo Enterprise for kagent | Build the Docker container image and push it to a container registry. |
| Agentic cloud platforms | AWS Bedrock AgentCore | Store the Dockerfile and source code in a GitHub repository. |
Before you begin
- Follow one of the Get started guides to install Solo Enterprise for agentregistry, set up the
arctlCLI, and connect a provider. - Create an MCP server.
- Build the Docker image or store the source code.
Publish the server
Update the
mcp.yamlfile 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, make sure that you have configured your credentials first. The example in this guide uses thehttps://github.com/solo-io/doc-examplessample 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 EOFPublish the MCP server to the Solo Enterprise for agentregistry catalog.
arctl apply -f mymcp/mcp.yamlExample output:
✓ MCPServer/mymcp createdVerify that the MCP server is published in the catalog.
arctl get mcpExample output:
NAME TAG DESCRIPTION mymcp latest mymcp MCP serverOptional: 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 providers.