Skip to content

Made minor fixes to README.md #119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jmhbh merged 1 commit into from
Feb 3, 2026
Merged

Made minor fixes to README.md #119

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,10 +54,10 @@

## Why kMCP?

Prototyping MCP services in isolation is quick and fun, but but production adoption introduces many challenges:
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.
- **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._**
Expand Down
Loading