MCP servers in Catalog

Uses: Catalog AI Gateway

Create an MCP server

Send a POST request to the /mcp-servers endpoint to create an empty MCP server:

MCP_ID=$(curl -X POST "https://us.api.konghq.com/v1/mcp-servers" \
     --no-progress-meter --fail-with-body  \
     -H "Authorization: Bearer $KONNECT_TOKEN" \
     --json '{
       "name": "my-mcp",
       "display_name": "My MCP",
       "description": "Customer support triage MCP server"
     }' | jq -r ".id"
)

Copied!

Add the MCP server’s capabilities and access methods by sending a POST request to the /mcp-servers/{mcpId}/versions endpoint:

curl -X POST "https://us.api.konghq.com/v1/mcp-servers/$MCP_ID/versions" \
     --no-progress-meter --fail-with-body  \
     -H "Authorization: Bearer $KONNECT_TOKEN" \
     --json '{
       "version": "1.0.0",
       "tools": [
         {
           "name": "get_forecast",
           "description": "Multi-day forecast for a location.",
           "input_schema": {
             "type": "object"
           }
         }
       ],
       "resources": [
         {
           "name": "forecast-docs",
           "uri": "file://forecast-docs.txt",
           "description": "Reference documentation describing forecast data fields and units.",
           "mime_type": "text/plain"
         }
       ],
       "prompts": [
         {
           "name": "summarize_forecast",
           "description": "Summarize the forecast for a location over a date range.",
           "arguments": [
             {
               "name": "location",
               "description": "The location to summarize the forecast for.",
               "required": true
             }
           ]
         }
       ],
       "remotes": [
         {
           "type": "streamable-http",
           "url": "https://mcp.example.com/weather"
         }
       ],
       "packages": [
         {
           "registry": {
             "type": "npm"
           },
           "identifier": "@example/weather-mcp-server",
           "version": "1.0.0",
           "transport": {
             "type": "stdio"
           }
         }
       ]
     }'

Copied!

(Optional) Link the MCP server to a server on AI Gateway by sending a POST request to the /mcp-servers/{mcpId}/implementations endpoint:

curl -X POST "https://us.api.konghq.com/v1/mcp-servers/$MCP_ID/implementations" \
     --no-progress-meter --fail-with-body  \
     -H "Authorization: Bearer $KONNECT_TOKEN" \
     --json '{
       "implementation": {
         "type": "ai-gateway",
         "config": {
           "gateway_control_plane_id": "'$CONTROL_PLANE_ID'",
           "gateway_mcp_server_id": "'$GATEWAY_MCP_SERVER_ID'"
         }
       }
     }'

Copied!

In the Konnect sidebar, click Catalog.
From the New dropdown menu, select MCP server.
Under Data source, select one of the following:
1. To fill out the server’s details yourself, select Define manually.
2. To populate details from an existing server’s definition, select Paste JSON, then in the Version, capabilities, and access methods field, paste the definition. Only version is required.
3. To create the server from an MCP interface already configured in AI Gateway 2.0, select Import from AI gateway, then:
  1. From the AI gateway dropdown menu, select your AI Gateway control plane.
  2. From the MCP server dropdown menu, select the server you want to import.
In the Display name field, enter a name for your MCP server, for example My MCP server.
In the Name field, enter a unique identifier for the MCP server, for example my-new-mcp-server. This must contain only lowercase letters, numbers, hyphens, and periods.
(Optional) In the Description field, describe the purpose of your MCP server.
(Optional) Click Add labels, and do the following:
1. In the Key field, enter a label key.
2. In the Value field, enter a label value.
3. (Optional) Click Add another label to add more labels.
Click Next.
If you didn’t select Paste JSON, in the Version field, enter a version number for your MCP server, for example 1.0.0.
(Optional) Under Capabilities, click New capability, and select one of the following:
- Tool: Outlines how your server takes actions.
  1. In the Name field, enter a unique identifier for the tool.
  2. In the Input schema field, enter the JSON schema defining the tool’s expected parameters.
  3. (Optional) Fill in Title, Description, Output schema, and Annotations.
  4. Click Add, then repeat to add more capabilities.
- Resource: To share server context through documents, logs, and other data.
  1. In the URI field, enter a unique identifier for the resource, for example file://example.txt.
  2. In the Name field, enter a name for the resource.
  3. (Optional) Fill in Title, Description, mimeType, and Size (bytes).
  4. Click Add, then repeat to add more capabilities.
- Prompt: Define a reusable workflow with preset inputs.
  1. In the Name field, enter a unique identifier for the prompt.
  2. (Optional) Fill in Title, Description, and a comma-separated list of Arguments, for example language, focus_area, severity_threshold.
  3. Click Add, then repeat to add more capabilities.
(Optional) Under Access methods, click New access method, and select one of the following:
- Remote: Describes a hosted MCP server endpoint.
  1. In the Remote URL field, enter the server’s endpoint, for example https://example.com/mcp.
  2. From the Transport type dropdown menu, select a transport type.
  3. (Optional) In the Headers field, enter headers as a JSON array of objects, for example, to pass an authorization token:
    [ { "name": "Authorization", "value": "Bearer ${token}" } ]
    
    Copied!
  4. Click Add, then repeat to add more access methods.
- Package, to describe a run-it-yourself distribution option.
  1. In the Package identifier field, enter the package name or URL, for example @modelcontextprotocol/mcp-server.
  2. From the Transport type and Package type dropdown menus, select the applicable types.
  3. (Optional) Fill in Registry base URL and Package version. If you leave Package version blank, the package uses the server’s version.
  4. Click Add, then repeat to add more access methods.
Click Save.

FAQs

Should I create an MCP server or MCP registry in the new Catalog?

If you’re creating a new MCP definition, create an MCP server. It’s the preferred object going forward, and is additive to the MCP registry’s server object. It captures remotes and packages like an MCP registry, but also supports the server’s tools, resources, and prompts. You can also link an MCP server to AI Gateway 2.0 as its source.

If you’re already using MCP registries, we recommend migrating to MCP server so you can use these additional capabilities. You can automate this by writing a script that iterates through each MCP registry and the MCP servers nested under it, then creates a new MCP server using the new object model for each one, including its remotes and packages. You won’t lose any information in the process, since the new object model is additive.

MCP servers in Catalog

Create an MCP server

FAQs

Help us make these docs great!

Still need help?