A MCP server for Operator Lifecycle Manager (OLM) v0, providing AI assistants with the ability to interact with OLM resources in Kubernetes clusters.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"olmv0-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 Model Context Protocol (MCP) server for Operator Lifecycle Manager (OLM) v0, providing AI assistants with the ability to interact with OLM resources in Kubernetes clusters.
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.
Be 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 / devops
MCP Server for GCP environment for interacting with various Observability APIs.
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP server for using the GitLab API
Heroku Platform MCP Server using the Heroku CLI
MCP Security Weekly
Get CVE alerts and security updates for Olmv0 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 Model Context Protocol (MCP) server for Operator Lifecycle Manager (OLM) v0, providing AI assistants with the ability to interact with OLM resources in Kubernetes clusters.
The OLM v0 MCP Server exposes OLM-specific resources and operations through the Model Context Protocol, allowing AI assistants to help users manage operators in their Kubernetes clusters. This server follows the same pattern as the kubernetes-mcp-server but focuses specifically on OLM v0 resources.
list_csvs: List ClusterServiceVersions in a namespaceget_csv: Get detailed information about a specific ClusterServiceVersionlist_subscriptions: List Subscriptions in a namespaceget_subscription: Get detailed information about a specific Subscriptionlist_catalog_sources: List CatalogSources in a namespaceget_catalog_source: Get detailed information about a specific CatalogSourcelist_install_plans: List InstallPlans in a namespaceget_install_plan: Get detailed information about a specific InstallPlanlist_tools: Show available tools and their parametersgit clone https://github.com/operator-framework/operator-lifecycle-manager.git
cd operator-lifecycle-manager/olmv0-mcp-server
make build
docker build -t olmv0-mcp-server .
# Start the server with default settings
./bin/olmv0-mcp-server
# Start on a specific port
./bin/olmv0-mcp-server --port 8080
# Use a specific kubeconfig
./bin/olmv0-mcp-server --kubeconfig /path/to/kubeconfig
# Enable only specific toolsets
./bin/olmv0-mcp-server --toolsets csv,subscription
--port, -p: HTTP/SSE server port (default: 8080)--kubeconfig: Path to kubeconfig file (default: $HOME/.kube/config)--read-only: Prevent write operations (default: true)--toolsets: Enable specific toolsets (default: csv,subscription,catalog,installplan)# Run with default settings
docker run --rm -p 8080:8080 \
-v ~/.kube/config:/root/.kube/config:ro \
olmv0-mcp-server
# Run with custom kubeconfig
docker run --rm -p 8080:8080 \
-v /path/to/kubeconfig:/kubeconfig:ro \
olmv0-mcp-server --kubeconfig /kubeconfig
curl -X POST http://localhost:8080 \
-H "Content-Type: application/json" \
-d '{
"method": "list_csvs",
"params": {
"namespace": "operators"
}
}'
curl -X POST http://localhost:8080 \
-H "Content-Type: application/json" \
-d '{
"method": "get_subscription",
"params": {
"name": "my-operator",
"namespace": "operators"
}
}'
curl -X POST http://localhost:8080 \
-H "Content-Type: application/json" \
-d '{
"method": "list_tools",
"params": {}
}'
# Download dependencies
make deps
# Build the binary
make build
# Run tests
make test
# Format code
make fmt
# Run linter
ma
... [View full README on GitHub](https://github.com/anik120/olmv0-mcp-server#readme)