# Connect agents to enterprise context
Build vendor-neutral and agent-ready interfaces for context across your API, event, and data store estates.
## Auto-discover APIs and data as tools
- *
Discover existing APIs and services that you have under Kong management, and leverage them as MCP tools.
- *
Leverage event data and event streams as real-time context for agents.
## Build in the GUI, or as code
- *
Add workflows and custom logic in Konnect and via IDE ecosystem.
## Only ship governed, discoverable MCP servers
- *
Register MCP tools and servers in the Konnect MCP registry.
- *
Make sure only enterprise-approved tools and servers are ever leveraged.
- *
Give agents a self-service catalog for discovering and consuming MCP servers and tools.
## Give agents thousands of capabilities — without thousands of tools
- *
Compose multiple API operations dynamically with Code Mode.
- *
Execute complex workflows with fewer model round trips.
- *
Keep context lean as your API and tool estate grows.
## Related products
## Resources
## Frequently Asked Questions
Questions teams ask before agents touch production APIs
What is Kong Context Mesh?
Kong Context Mesh connects AI agents to enterprise context through vendor-neutral, agent-ready interfaces across APIs, events, and data stores. It helps teams make existing services available as tools that agents can discover and use.
Can Context Mesh make our existing APIs available to AI agents?
Yes. Context Mesh discovers existing APIs and services under Kong management and makes them available as MCP tools. This lets you use your existing API infrastructure to provide agents with enterprise capabilities.
Can Context Mesh provide real-time context for agents?
Yes. Context Mesh enables agents to use event data and event streams as real-time context. Kong Event Gateway complements this by turning governed event streams into context for event-driven agents.
How can we control which tools and servers agents use?
Context Mesh uses the Konnect MCP registry to register MCP tools and servers and ensure that only enterprise-approved options are used. The registry also gives agents a self-service catalog for discovering and consuming approved servers and tools.
How does Context Mesh keep agent context manageable as our API estate grows?
Context Mesh includes Code Mode, which lets agents dynamically compose multiple API operations without requiring thousands of individual tools. It supports complex workflows with fewer model round trips and keeps context lean as your APIs and tools grow.
Can teams build workflows visually or in code?
Context Mesh supports both approaches. Teams can add workflows and custom logic through the Konnect graphical interface or work through the IDE ecosystem.
Is Context Mesh tied to a specific agent vendor?
Context Mesh is designed to provide vendor-neutral, agent-ready interfaces for enterprise context. It makes APIs and services available as MCP tools rather than tying those interfaces to a specific agent vendor.
How does Context Mesh work with Kong AI Gateway?
Context Mesh connects agents to enterprise APIs, services, and context through agent-ready interfaces, including MCP. Kong AI Gateway complements this by governing the AI and agent traffic that flows across models, agents, tools, and MCP servers. Together, they help enterprises connect agents to the capabilities they need while maintaining control over how those capabilities are accessed and used