From efecfffd1bddc0ed9bf669948c24a0881a0ebd50 Mon Sep 17 00:00:00 2001 From: Ram Iyengar Date: Mon, 2 Feb 2026 16:11:40 +0530 Subject: [PATCH] Made minor fixes to README.md Signed-off-by: Ram Iyengar --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 617effa..59acc69 100644 --- a/README.md +++ b/README.md @@ -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._**