---
title: "Create MCP implementation"
method: POST
path: "/v1/mcp-servers/{mcpId}/implementations"
tags: ["Catalog MCP Implementations"]
---

# Create MCP implementation

`POST /v1/mcp-servers/{mcpId}/implementations`

Creates an implementation record for the MCP. Returns `409` if the MCP has an existing implementation.

## Request body

- CreateCatalogMCPImplementation — Request body for creating an MCP implementation linked to an AI Gateway MCP Server.
  - `implementation` CatalogMCPGatewayImplementationBlock, required — Schema to describe the type and configuration typing for an MCP implementation linked to an AI Gateway MCP Server.
    - `type` 'ai-gateway', required
    - `config` CatalogMCPGatewayImplementationConfig, required — Configuration for an MCP implementation linked to an AI Gateway MCP Server.
      - `gateway_control_plane_id` string, uuid, required — The AI Gateway control plane the linked model belongs to.
      - `gateway_mcp_server_id` string, required — The identifier of the linked AI Gateway MCP server.

## Response `201`

Response schema for MCP implementations.

- CatalogMCPImplementation — Base schema for MCP implementations.
  - `id` string, uuid, required — The unique identifier of the implementation (link) record.
  - `created_at` string, date-time, required — An ISO-8601 timestamp representation of entity creation date.
  - `updated_at` string, date-time, required — An ISO-8601 timestamp representation of entity update date.
  - `implementation` CatalogMCPGatewayImplementationBlock, required — Schema to describe the type and configuration typing for an MCP implementation linked to an AI Gateway MCP Server.
    - `type` 'ai-gateway', required
    - `config` CatalogMCPGatewayImplementationConfig, required — Configuration for an MCP implementation linked to an AI Gateway MCP Server.
      - `gateway_control_plane_id` string, uuid, required — The AI Gateway control plane the linked model belongs to.
      - `gateway_mcp_server_id` string, required — The identifier of the linked AI Gateway MCP server.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict

## Changes

- **2026-09-30** `f530bf400198` — 4 warning
  - added the new `400.00` enum value to the `status` response property for the response status `400`
  - added the new `403.00` enum value to the `status` response property for the response status `403`
  - added the new `404.00` enum value to the `status` response property for the response status `404`
  - added the new `409.00` enum value to the `status` response property for the response status `409`
- **2026-09-25** `4a02153f2e60` — 4 breaking, 30 info
  - the response's body type changed from no type to `object` for status `400`
  - the response's body type changed from no type to `object` for status `403`
  - the response's body type changed from no type to `object` for status `404`
  - the response's body type changed from no type to `object` for status `409`
  - …30 more
- **2026-09-18** `5ca78660b97c` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/kong/apis/konnect-api/changes/v1/mcp-servers/:mcpId/implementations/post.md)

---

[API](https://skmtc.dev/kong/apis/konnect-api.md) · [All operations](https://skmtc.dev/kong/apis/konnect-api/llms.txt) · [OpenAPI document](https://skmtc.dev/kong/apis/konnect-api/revisions/f530bf400198?raw)