The Kong Konnect MCP server, built by Kong, provides the first thing to know about Kong and MCP is that the community repository most directories still link to — Kong/mcp-konnect — is deprecated. It is no longer maintained and best for API & Web.
by Kong
This repository is archived
GitHub reports the repository below as archived, so it takes no further commits, issues or pull requests — but the published package has not been unpublished, so Remote server — connect to Kong's hosted Konnect MCP endpoint (see developer.konghq.com/konnect-platform/konnect-mcp/). The old npx @kong/mcp-server package does not exist on npm. still installs and runs. Read the section below before you build on it: where a maintained replacement exists, it is named there.
About
The first thing to know about Kong and MCP is that the community repository most directories still link to — Kong/mcp-konnect — is deprecated. Its README now carries a maintenance warning: no further updates, bug fixes or features, issues and pull requests unmonitored, and the repo is headed for read-only archive. Kong's supported path is the Konnect remote MCP server, documented at developer.konghq.com/konnect-platform/konnect-mcp/, which is hosted by Kong rather than installed locally, so there is no npm package to run and nothing to keep patched on your side. The capability set both cover is the same: let an AI assistant query and analyze a Kong Gateway estate through Konnect. That means API request analytics with customizable filters (time windows, status codes, routes, consumers), inspection of gateway configuration objects — services, routes, consumers and plugins — and management of control planes and control plane groups. The practical use is diagnostic rather than mutating: asking which routes returned 5xx in the last hour, which consumer is driving traffic to a given service, or which plugins are attached where, without building a dashboard query for each question. Kong sits in an unusual spot in the MCP gateway conversation because it is both a subject and a peer: Kong Gateway is itself an API gateway that can front MCP traffic (Kong publishes AI-gateway guidance for exactly that, including an AWS reference architecture for GenAI MCP and A2A gateways), while this entry is the MCP server that lets an agent administer Konnect. If you arrived looking for "kong mcp gateway" you probably want the former; if you want your agent to read Konnect analytics, you want the remote server here. Node.js 20+ and a Konnect account with API access were the prerequisites for the deprecated local build.
Trust verdict
How grades are computed →Grade E (30/100, at risk) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance0/100 · weight 20
The repository is archived by its owner, so it is by definition no longer maintained.
- Source verification15/100 · weight 25
The repository resolves, but its owner has archived it. Archived means read-only: no fixes, no releases, no response to issues.
- Provenance90/100 · weight 10
Published and maintained by the vendor of the service it connects to, rather than by a third party.
- Listing ↔ repository match100/100 · weight 5
The listing name lines up with the linked repository Kong/mcp-konnect.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Installation
Remote server — connect to Kong's hosted Konnect MCP endpoint (see developer.konghq.com/konnect-platform/konnect-mcp/). The old npx @kong/mcp-server package does not exist on npm.This command will fail: @kong/mcp-server was not published to the npm registry when we checked on August 17, 2026. Install from the repository below instead.
Categories
Works With
Frequently Asked Questions
What is Kong Konnect MCP Server?
Who built Kong Konnect MCP Server?
Is Kong Konnect MCP Server free?
How do I install Kong Konnect MCP Server?
What does Kong Konnect MCP Server integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 3mo ago
- Install
- npm
- Package
- @kong/mcp-server
Quick Info
- Install Type
- npm
- Author
- Kong
- Categories
- 3
- Integrations
- 3
Related Servers
Fetch
Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.
Git
Tools to read, search, and manipulate Git repositories. Full Git operations support.
Apify MCP Server
The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.
GitHub MCP Server
authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.
GitLab MCP Server
a first-party MCP endpoint built into the GitLab instance itself — there is no package to install, because the server ships inside GitLab and answers at https://<your-gitlab>/api/v4/mcp (gitlab.com exposes the same path, so https://gitlab.com/api/v4/mcp works for SaaS projects). It landed as an experiment in GitLab 18.3 and moved to beta in 18.6. Authentication is the part that makes it different from every community GitLab server: it uses OAuth 2.0 Dynamic Client Registration, so the first time a client connects it registers itself as an OAuth application on your instance and is issued an access token — no personal access token pasted into a config file. Administrators who do not want one OAuth application per tool can pre-create a shared application instead. Three prerequisites are what actually block most first connections: GitLab Duo must be set to Always on or On by default, beta and experimental features must be enabled, and MCP access must be switched on at the group or instance level. The tool surface covers issues and merge requests (create_issue, get_issue, create_merge_request, get_merge_request, list_merge_requests, get_merge_request_commits, get_merge_request_diffs, get_merge_request_pipelines, create_merge_request_note, get_merge_request_notes), CI/CD (manage_pipeline for list/create/delete/retry/cancel, get_pipeline_jobs, get_job_log), work items (create_workitem_note, get_workitem_notes, link_work_items, get_saved_view_work_items), search (search across the instance, search_labels, semantic_code_search), list_wiki_pages, and attach_scan_profile. HTTP is the recommended transport — claude mcp add --transport http GitLab https://gitlab.com/api/v4/mcp — and clients that only speak stdio can wrap it with npx mcp-remote <url> on Node 20+. Send the X-Gitlab-Mcp-Server-Tool-Name-Prefix header if generic names like search collide with another connected server. If your instance predates 18.3 or Duo is not available to you, the community alternative most teams land on is zereight/gitlab-mcp (1,889 stars as of 2026-08-16, npm @zereight/mcp-gitlab), which authenticates with a plain personal access token and ships 217 tools — including merge_merge_request, approve_merge_request, execute_graphql and full CI/CD variable management, none of which the built-in server exposes — behind GITLAB_PERMISSION_MODE=readonly/modify and GITLAB_TOOLSETS/GITLAB_TOOLS filtering. One further change worth noting: MCP server access moved from GitLab Premium to GitLab Free in 19.2 and became a setting of its own.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →