Skip to content

Kong Konnect MCP connector

The Kong Konnect connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent search your gateway services, routes, and consumers, look up how each one works, and make approved changes, with every call signed in as you and logged.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which routes point at the payments service in production?

Working in Kong Konnect with Elaichi

  • Search
  • Get schema
  • Execute
Ask anything…
Governance / Audit log Last 24 hours
Kong Konnect Execute Emily Carter · ChatGPT · 9:41 AM Done
Kong Konnect Get schema Emily Carter · ChatGPT · 9:41 AM Done
Kong Konnect Search Emily Carter · ChatGPT · 9:41 AM Done
Kong Konnect Search Megan Brooks · Claude · 9:38 AM Done
Kong Konnect Search Ryan Hayes · Cursor · 9:35 AM Done

How to connect Kong Konnect to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Kong Konnect MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Kong Konnect MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Kong Konnect MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Kong Konnect MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Kong Konnect MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Kong Konnect to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Kong Konnect through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Kong Konnect is logged.

  • Platform

    Find which route fronts a service

    Ask which gateway routes point at a service and which consumers call it, then make the change while the conversation is still open.

  • Security

    Check who holds a consumer credential

    List the consumers on a control plane, see which plugins guard them, and tighten a rate limit or auth plugin from the chat.

  • API product

    Keep the API catalog current

    Look up an API product in Kong Konnect, check what is published to the developer portal, and update the description without opening the console.

  • Support

    Answer a partner's access question

    When a partner says their key stopped working, find their consumer, see the plugins on their route, and fix what is blocking them.

  • Operations

    Roll out a plugin change across routes

    Ask what fields a rate limiting plugin accepts, then apply the same setting to every route that needs it.

  • Developer relations

    Onboard a new team to the gateway

    Register their service and routes, add a consumer, and hand back a plain summary of everything that was created.

Try asking

  • “Which routes point at the payments service in production?”
  • “List consumers on the partner control plane without a rate limit plugin.”
  • “Add a consumer for Acme and attach the key auth plugin.”

See all 3 Kong Konnect tools →

What connecting Kong Konnect gets you

6 screens from Elaichi, each doing one job for your Kong Konnect account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which routes point at the payments service in production?

List consumers on the partner control plane without a rate limit plugin.

Add a consumer for Acme and attach the key auth plugin.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about your gateways in plain language.

Services, routes, and consumers from Kong Konnect, answered from live records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint reaches Kong Konnect from every client.

Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
Search Search Finds relevant API operations based on a description of what you want to do (e.g. "list all services in a control plane").
Get schema Get Retrieves the full/partial (as required) schema for a specific operation, so the AI knows exactly what parameters and request body fields are required.
Execute Execute Calls the API operation with the appropriate inputs, based on what get_schema returned.

Tool catalog

3 tools cover search, schema, and execute.

Search Kong Konnect, look up any field, and run the change, with no custom code.

ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Kong Konnect · control planes and gateways

Kong Konnect starter 18 Mar 4, 2026

Security toolbox

Kong Konnect · consumers and auth plugins

— 9 Mar 2, 2026

API product toolbox

Kong Konnect · API products and the developer portal

— 24 Feb 27, 2026

Support toolbox

Kong Konnect · partner consumers and keys

Kong Konnect starter 6 Feb 19, 2026

Operations toolbox

Kong Konnect · routes and rate limits

— 31 Jan 30, 2026

Developer relations toolbox

Kong Konnect · onboarding services and docs

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Kong Konnect toolbox.

Platform, security, and support each work from a toolbox scoped to their job.

ElaichiConnections
Connection Scope Status Access
KO

Kong Konnect (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
KO

Kong Konnect (Security)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
KO

Kong Konnect (Production)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
KO

Kong Konnect (Partner APIs)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
KO

Kong Konnect (Support)

Connected by Ryan Hayes

Personal • Active Not shared
KO

Kong Konnect (Sandbox)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use the connection, never the credential.

See who connected Kong Konnect and which teams and members work through it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Kong Konnect Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Kong Konnect Services Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Kong Konnect Services List Toolbox

Audit log

Every Kong Konnect change names the person.

When, who, what happened, type, and resource, kept in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Kong Konnect digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch services

    Kong Konnect

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Kong Konnect

    Queued

Workflows

A schedule starts the work, a person approves.

Consumers are fetched, grouped, drafted into a digest, approved, then posted back to Kong Konnect.

Kong Konnect health

Refreshed 4 minutes ago · every 15 minutes · from the services collection

Live

Services

1,284 ↓ 12%

Routes

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Services created

Last 14 days

By team

Share of activity

Platform 34%

Security 27%

Production 21%

Partner APIs 18%

Collections and dashboards

Kong Konnect health, counted without a model.

Four metrics, fourteen days of routes created, and a breakdown by team, refreshed on schedule.

Why connect Kong Konnect's MCP server through Elaichi

Kong Konnect builds and runs this MCP server. Elaichi sits in front of it, so Kong Konnect's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Kong Konnect's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Kong Konnect's tools at the same Elaichi address as every other connected app. Nobody adds Kong Konnect's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Kong Konnect sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Kong Konnect's server. By default, a tool Kong Konnect does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Kong Konnect

    Kong Konnect builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Kong Konnect team.

    support.konghq.com/support/s

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Kong Konnect

All three can connect Kong Konnect to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Kong Konnect, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Kong Konnect tools Allow or restrict single Kong Konnect tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Kong Konnect call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Kong Konnect tools for your AI agents

3 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kong Konnect, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Kong Konnect builds and runs these tools.

Questions, answered

How do I connect Kong Konnect to Claude?

Open Elaichi, pick Kong Konnect from the catalog, and sign in to Kong Konnect over OAuth; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Kong Konnect is ready to use.

Does Kong Konnect work with ChatGPT and Cursor as well as Claude?

Yes. Kong Konnect is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. Connect it once and every client you use sees it.

What can an AI agent actually do with my Kong Konnect data?

It can search across your Kong Konnect control planes for services, routes, consumers, and plugins, look up what fields each one takes, and make a change you ask for, such as adding a consumer or adjusting a rate limit. Short, concrete asks work better than long sentences: "show me the routes on the payments service" gets a cleaner answer than a paragraph.

Does connecting Kong Konnect give the AI every control plane?

No. The AI works inside the Kong Konnect access of whoever signed in, so it only sees the control planes, services, and consumers that person can already open. Elaichi can narrow that further, for example to searching and reading only, but it can never widen it beyond what Kong Konnect granted.

Can my team share one Kong Konnect connection?

Yes. One person connects Kong Konnect and shares it with a team in Elaichi, and nobody else ever handles a token. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind each change to a service or plugin.

Can I stop an agent from deleting or changing things in Kong Konnect?

Yes. Restrictions in Elaichi are set per action, so you can allow searching and looking up Kong Konnect services while restricting anything that creates, edits, or deletes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude or any other client cannot run it, whatever the prompt says.

What happens to a Kong Konnect connection when someone leaves?

Offboarding the person in Elaichi ends their access to Kong Konnect through every client at once. A connection they shared keeps working for everyone else on the team. Disconnecting Kong Konnect once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent together.

Does the Kong Konnect MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Kong Konnect is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Kong Konnect?

Yes. Both let Claude, ChatGPT or Cursor use Kong Konnect. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Kong Konnect call.

How is Elaichi different from Composio for Kong Konnect?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Kong Konnect: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Kong Konnect in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot