AI MCP Proxy

AI License Required

Configure consumer groups and key authentication for per-tool MCP access control

Configure consumer groups and key authentication to control access to individual MCP tools based on consumer roles. This configuration applies access control rules at the tool level without a default policy.

For this configuration to work properly, you need to create the following Kong Gateway entities:

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

plugins:
  - name: key-auth
    route: mcp-route
    config:
      key_names:
        - apikey

consumer_groups:
  - name: admin
  - name: developer
  - name: suspended

consumers:
  - username: alice
    groups:
      - name: admin
    keyauth_credentials:
      - key: alice-key

  - username: bob
    groups:
      - name: developer
    keyauth_credentials:
      - key: bob-key

  - username: carol
    groups:
      - name: suspended
    keyauth_credentials:
      - key: carol-key

  - username: eason
    keyauth_credentials:
      - key: eason-key

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

Prerequisites

  • A running and exposed API

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!