Home / Companies / Kong / Blog / Post Details
Content Deep Dive

Kong AI/MCP Gateway and Kong MCP Server Technical Breakdown

Blog post from Kong

Post Details
Company
Date Published
Author
Claudio Acquaviva and Jason Matis
Word Count
3,592
Company Posts That Month
11
Language
English
Hacker News Points
-
Post removed?
No
Summary

The blog post delves into the Model Context Protocol (MCP) and its integration with Kong's AI Gateway to streamline the interaction between AI agents and enterprise systems. It highlights the role of MCP in managing data flow to prevent information overload in AI systems, allowing for standardized and efficient data processing. The Kong Gateway 3.12 release introduces several MCP capabilities, including the AI MCP Proxy and OAuth2 plugins, to facilitate secure and seamless communication between MCP clients and servers. These plugins enable the conversion of existing Kong Gateway services into MCP tools, providing real-time visibility, reducing vulnerabilities, and supporting advanced agentic patterns such as multi-step workflows and contextual enrichment. The article also discusses the architecture of MCP, detailing its client-server model and the transport mechanisms based on JSON-RPC 2.0, such as Stdio and Streamable HTTP. The integration of security measures like OAuth2 ensures that MCP tool endpoints remain protected, further enhancing the scalability and reliability of AI deployments. The post encourages exploring Kong’s flexible plugin ecosystem and its partnership with AWS to build secure and scalable MCP-enabled architectures.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
MCP 175 4,899 392 145 +47%
Kubernetes 6 1,540 251 91 +19%
Platform Engineering 5 413 123 52 -15%
AI Agents 4 2,834 598 185 -18%
Secrets Management 3 1,206 193 82 -5%
LLM 2 3,775 638 202 -32%
Observability 2 2,671 527 151 +5%
Real-time 2 7,285 1,202 224 +60%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.