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

Register a remote MCP server in the Solo Enterprise for agentregistry catalog and attach it to a deployed agent so that the agent can call the server’s tools.

You can extend any deployed agent by connecting it to a remote MCP server. A remote MCP server is an MCP tool server that is already running at a publicly accessible URL and does not need to be built or deployed by Solo Enterprise for agentregistry. When you register the server in the catalog and reference it in your agent’s definition, Solo Enterprise for agentregistry automatically makes the server’s tools available to the agent at runtime.

Before you begin

• Follow one of the get started guides to install Solo Enterprise for agentregistry, connect to your preferred runtime, and deploy your first agent.
• Get the URL of the remote MCP server, including the path. For example, your MCP URL might look as follows: https://my-mcp-server.example.com/mcp.

Step 1: Register the remote MCP server

1. Create a registry catalog entry for the remote MCP server. The example in this guide uses the MCP test server https://test-mcp.are.soloio.dev/mcp that is provided by Solo.io. This server exposes two tools, an echo and an add tool.

   arctl apply -f - <<EOF
   apiVersion: ar.dev/v1alpha1
   kind: MCPServer
   metadata:
     name: myorg/remotemcp
   spec:
     description: Remote MCP server
     remote:
       type: streamable-http
       url: https://test-mcp.are.soloio.dev/mcp
   EOF

   Field	Description
   metadata.name	The catalog name for the server. Use the <org>/<name> format.
   spec.remote.type	The transport type. Use streamable-http for HTTP-based MCP servers.
   spec.remote.url	The full URL of the remote MCP server, including the path (for example, /mcp).

   Example output:

   ✓ MCPServer/myorg/remotemcp created
   

2. Verify that the remote MCP server is registered in the catalog.

   arctl get mcp

   Example output:

   NAME                 TAG      DESCRIPTION
   myorg/remotemcp      latest   Remote MCP server
   mymcp                latest   Sample MCP server
   

Step 2: Add the MCP server to your agent

1. Update the agent’s agent.yaml to reference the remote MCP server in the mcpServers list. You can reference multiple MCP servers.

   cat > myagent/agent.yaml <<EOF
   apiVersion: ar.dev/v1alpha1
   kind: Agent
   metadata:
     name: myagent
   spec:
     source:
       image: localhost:5001/myagent:latest
       repository:
         url: https://github.com/solo-io/doc-examples
         subfolder: agentregistry/myagent
     modelProvider: bedrock
     modelName: us.anthropic.claude-sonnet-4-6
     description: myagent agent
     mcpServers:
       - kind: MCPServer
         name: mymcp
       - kind: MCPServer
         name: myorg/remotemcp
   EOF

2. Re-publish the updated agent to the registry.

   arctl apply -f myagent/agent.yaml

   Example output:

   ✓ Agent/myagent (latest) updated
   

Step 3: Deploy the agent

Follow the steps to deploy or re-deploy the agent to your runtime.