Kong Konnect

com.konghqPublished by konghq.comOfficial publisherv1.0.0Updated Oct 24, 2026

Manage Kong Konnect AI and API gateways, routes, plugins, and analytics from your agent.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureData & Analytics

Overview

AI-generated overview

Lets an assistant manage Kong Konnect AI and API gateways, routes, plugins, and analytics from the agent.

What you can do
This remote MCP server connects an assistant to Kong Konnect, Kong's API management platform. According to the registry description, it covers managing AI and API gateways, routes, plugins, and analytics. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when an assistant should inspect or change Kong Konnect gateway configuration — gateways, routes, plugins — or pull gateway analytics, instead of working through the Konnect UI or API by hand.
Requirements
A remote streamable HTTP endpoint at no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to a Kong Konnect account, and the described scope includes managing gateways, routes, and plugins, so configuration-changing actions may be possible; review the granted scopes and prefer read-only access where sufficient. Analytics data is sent to the remote endpoint.

Installation

In SourceWeft

  1. Open Kong Konnect in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.konghq%2Fkonnect/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "kong-konnect": {
      "type": "http",
      "url": "https://global.mcp.konghq.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.