Kong Konnect MCP connector
The Kong Konnect connector lets Claude, ChatGPT, Cursor, 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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
3 tools
How to connect
How to connect Kong Konnect to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Kong Konnect once
-
Open Connections, choose Add connection, and pick Kong Konnect.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Kong Konnect. Kong Konnect's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Kong Konnect MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Kong Konnect MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect Kong Konnect to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with Kong Konnect through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
Compare
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.
| 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 | $15 per user per month. | 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.
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting Kong Konnect gets you
6 screens from the product, each doing one job for your Kong Konnect account.
The agent
Ask about your gateways in plain language.
Services, routes, and consumers from Kong Konnect, answered from live records.
- services
- routes
- consumers
- plugins
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 or Cursor
MCP clients
One endpoint reaches Kong Konnect from every client.
Claude, ChatGPT, and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
3 tools cover search, schema, and execute.
Search Kong Konnect, look up any field, and run the change, with no custom code.
- Search
- Get schema
- Execute
ElaichiToolsToolboxes
Each team gets its own Kong Konnect toolbox.
Platform, security, and support each work from a toolbox scoped to their job.
- Platform
- Security
- API product
- Support
ElaichiToolboxesShared connections
Teammates use the connection, never the credential.
See who connected Kong Konnect and which teams and members work through it.
- Platform
- Security
- Production
- Partner APIs
ElaichiConnectionsAudit log
Every Kong Konnect change names the person.
When, who, what happened, type, and resource, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
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 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch services
Kong Konnect
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Kong Konnect
Queued
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.
Kong Konnect health
Refreshed 4 minutes ago · every 15 minutes · from the services collection
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%
FAQ
Frequently asked questions
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, 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 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 blocking anything that creates, edits, or deletes. A restricted action is never advertised to Claude or any other client, so no prompt, however worded, can reach it.
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, 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.