Kong / Kong/developer.konghq.com

Migrate AI MCP Proxy examples

Open
#6,760 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

internal product:ai-gateway
Dominant language
Ruby
Stars
28
Forks
121
Avg merge
1d 4h
Merged PRs (30d)
313

Description

Overview

AI MCP Proxy is no longer a standalone plugin concept in AI Gateway 2.0. Migrate the existing [AI MCP Proxy configuration examples](https://developer.konghq.com/plugins/ai-mcp-proxy/examples/) to the new AI Gateway 2.0 entity model.

The existing examples rely heavily on Gateway Services, Routes, and plugin attachment. These need to be reworked for the new MCP entity model.

Scope

Inventory and migrate the supported AI MCP Proxy examples.

For each migrated example:

  • Use the appropriate AI Gateway 2.0 MCP entities.
  • Remove dependencies on Gateway Services, Routes, and ai-mcp-proxy.
  • Provide Konnect API and kongctl configuration.
  • Preserve the intent of the original example rather than its old configuration structure.
  • Validate the example against the AI Gateway 2.0 schema.

Common Petstore setup

As part of this ticket, evaluate using a shared Petstore API as the upstream for the migrated examples.

A starting point should be a locally runnable Petstore:

docker run --rm \
  --name petstore \
  -p 8080:8080 \
  swaggerapi/petstore3:unstable

Notes

Research and decide where these examples should live in the AI Gateway 2.0 documentation.

AI MCP Proxy no longer provides a natural documentation container. Consider a landing/reference page for MCP configuration examples, linked from the relevant MCP entity pages.

Final placement is TBD and part of this ticket.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the linked AI MCP Proxy configuration examples and inventory the supported cases to migrate. Run the provided Docker Petstore command as a possible shared upstream, then validate each Konnect API and kongctl example against the AI Gateway 2.0 schema. Done means the examples use MCP entities without Gateway Services, Routes, or ai-mcp-proxy, while preserving their original intent and documenting their final placement.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
api, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.