A Kubernetes-native MCP server that discovers internal microservices, extracts their OpenAPI specs, and exposes type-safe MCP tools for API introspection and in-cluster endpoint invocation.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"openapi-k8s-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Kubernetes-native MCP server that discovers internal microservices, extracts their OpenAPI specs, and exposes type-safe MCP tools for API introspection and in-cluster endpoint invocation.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for Openapi K8s Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A lightweight MCP (Model Context Protocol) server that runs inside your Kubernetes cluster, crawls your Services and endpoints via the Kubernetes API, auto-detects exposed OpenAPI specs, and builds a live, queryable index of your entire microservice surface area. It normalizes each spec (derefs, merges, fixes inconsistencies), tracks versions, and exposes the whole thing as MCP tools so agents can introspect, list, and invoke endpoints directly over in-cluster networking — essentially turning your microservices into a distributed, self-describing function registry.
| Feature | Status |
|---|---|
| Service discovery via K8s API | ✅ Done |
| OpenAPI 3.x spec fetching & parsing | ✅ Done |
| Persistence in embedded Derby | ✅ Done |
| Basic MCP tools (list, get, invoke) | ✅ Done |
| Rate limiting & exponential backoff | ✅ Done |
| Configurable URL templates | ✅ Done |
| OpenAPI 2.0 / Swagger support | 🚧 Planned |
| Authentication to target services | 🚧 Planned |
| MCP authentication / role-based access | 🚧 Planned |
| Minimal status UI | 💭 Maybe later |
┌────────────────────────────────────────────────────────────────┐
│ MCP Server │
├────────────────────────────────────────────────────────────────┤
│ ┌──────────────┐ ┌──────────────┐ ┌────────────────────┐ │
│ │ K8s Discovery│ │OpenAPI Parser│ │ MCP Tools Layer │ │
│ │ Service │──│ Service │──│ │ │
│ └──────────────┘ └──────────────┘ │ - list_services │ │
│ │ │ │ - get_operations │ │
│ ▼ ▼ │ - invoke_endpoint │ │
│ ┌──────────────────────────────┐ │ - get_op_details │ │
│ │ Derby (Embedded) │ └────────────────────┘ │
│ │ - discovered_services │ │
│ │ - openapi_specifications │ │
│ └──────────────────────────────┘ │
│ ▲ │
│ ┌──────────────┐ │
│ │ Scheduler │ ← Refresh every 10 minutes │
│ └──────────────┘ │
└───────────────────────────────────────────────────────────────-┘
mvn clean package
# With local kubeconfig
java -jar target/openapi-mcp-server-*.jar
# With custom config
KUBECONFIG=/path/to/config java -jar target/openapi-mcp-server-*.jar
docker build -t openapi-mcp-server .
docker run -v ~/.kube/config:/root/.kube/config:ro openapi-mcp-server
The k8s/ directory contains all the manifests needed to deploy the MCP server inside a Kubernetes cluster.
kubectl configured wit