AI MCP Proxy

AI License Required

Aggregate MCP tools from conversion-only mode plugins

Listener mode works together with conversion-only mode:

  • Configure one or more Routes with the plugin in conversion-only mode. Each conversion-only Route defines tools and assigns them a tags[] value.
  • Configure a separate Route for the plugin in the listener mode:

    services:
    - name: mcp-service
      url: http://host.docker.internal:3000
      routes:
      - name: mcp-listener
        paths:
        - /mcp-listener
    

    Before using the AI MCP Proxy plugin, you’ll need an upstream HTTP API to expose. Use this mock API to test the plugin without relying on an external service; it simulates a small marketplace with sample users and orders exposed through /marketplace/users and /marketplace/{userId}/orders endpoints:

    curl -s -o api.js "https://gist.githubusercontent.com/subnetmarco/5ddb23876f9ce7165df17f9216f75cce/raw/a44a947d69e6f597465050cc595b6abf4db2fbea/api.js"
    npm install express
    node api.js
    

    The listener uses config.server.tag to bind all matching conversion-only tools into a single MCP server based on tags[] defined in the conversion-only plugin(s) defined on the plugin level.

    Check the Aggregate MCP tools from multiple AI MCP Proxy plugins how-to for a detailed walkthrough.

Prerequisites

  • At least one Route with the plugin in conversion-only mode, tagged at the plugin level with the same value as config.server.tag

Set up the plugin

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!