<!-- markdownlint-disable MD033 --> <table align="center"> <tr> <td> <a href="#getting-started"><b><i>Getting Started</i></b></a> </td> <td> <a href="#from-prototype-to-production"><b><i>Prototype to Production</i><b></a> </td> <td> <a href="#technical-details"><b><i>Technical Details</i></b></a> </td> <td> <a href="#get-involved"><b><i>Get Involved</i></b></a> </td> <td> <a href="#reference"><b><i>Reference</i></b></a> </td> </tr> </table> <!-- markdownlint-disable MD033 -->
Why kMCP?
Prototyping MCP services in isolation is quick and fun, but production adoption introduces many challenges:
- Ad-hoc scaffolding - Configuring the MCP server, integrating it in Kubernetes, and operating it at enterprise scale
- Transport fragmentation – Supporting multiple protocols (HTTP, WebSocket, SSE, etc.) requires custom maintenance
- Disconnected context - Enforcing consistent security, observability, and governance for agent-to-tool communication
We believe teams who have build MCP services should not experience friction when bringing those services to production. kMCP is designed to make MCP connectivity simple.
Getting Started
Install the kmcp CLI on your local machine.
curl -fsSL https://raw.githubusercontent.com/kagent-dev/kmcp/refs/heads/main/scripts/get-kmcp.sh | bash
Verify that the kmcp CLI is installed.
kmcp --help
You're ready to go! Continue on to From Prototype to Production or explore our docs at kagent.dev/docs/kmcp
From Prototype to Production
<img src="img/kmcp.png" alt="kmcp architecture" width="800">MCP connectivity affects everyone in an organization. Below are some common quickstart journeys that you may experience:
- Your first MCP service prototype
- AI/ML Engineer packaging an existing prototype
- DevOps engineer building MCP infrastructure in Kubernetes
Technical Details
kmcp is a comprehensive toolkit for building, deploying, and managing Model Context Protocol (MCP) servers. For a more detailed breakdown of using kmcp in your workflow, check out our achitecture overview.
Core Components
- CLI is your primary tool for development. It allows you to scaffold new MCP projects, manage tools, build container images, and run your MCP server locally for testing and development.
- Controller: Manages the lifecycle of your MCP server deployments in your Kubernetes cluster. It uses a Custom Resource Definition (CRD) to define MCP servers as native Kubernetes objects, allowing you to manage them with familiar
kubectlcommands. - Transport Adapater - Fronts the MCP server and provides features such as external traffic routing for your MCP server with support for multiple transport protocols without requiring any changes to your code.
Core Principles
- ✨ Rapid scaffolding with support for FastMCP (Python) and MCP Go SDK
- 🚀 One-command deployment to Kubernetes with pre-configured Transport Adapters
- 🔄 Consistent workflow from local development to production
- 🌐 Built-in transport support for HTTP, WebSocket, and Server-Sent Events
- ☸️ Kubernetes-native using Custom Resource Definitions (CRDs)
- 🔐 Secrets management integrated with Kubernetes secrets
Get Involved
We welcome contributions! Contributors are expected to respect the kagent Code of Conduct
There are many ways to get involved:
- 🐛 Report bugs and issues
- 💡 Suggest new features
- 📖 Improve documentation
- 🔧 Submit pull requests
- ⭐ Star the repository
- 💬 Help others in Discord
- 💬 Join the kagent community meetings
- 🤝 Share tips in the CNCF #kagent slack channel
- 🔒 Report security concerns
Thanks to all contributors!
<a href="https://github.com/kagent-dev/kmcp/graphs/contributors"> <img alt="kmcp contributors" src="https://contrib.rocks/image?repo=kagent-dev/kmcp" /> </a>Reference
Resources
Ecosystem Resources
- Model Context Protocol Specification
- MCP Documentation
- Anthropic's MCP Announcement
- FastMCP Python Documentation
- MCP Go SDK
License
This project is licensed under the Apache 2.0 License.
<div align="center"> <p>Built with ❤️ by the <a href="https://github.com/kagent-dev">kagent team</a> </p> </div>