MCP Server providing various tools for working with a Control Plane
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"controlplane-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.
Read Events: Look up events corresponding to the supplied pod. Read Pod Logs: Look up logs corresponding to the supplied pod.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
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 devops
MCP server for using the GitLab API
Enhanced MCP server for GitLab: group projects listing and activity tracking
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
MCP Security Weekly
Get CVE alerts and security updates for Controlplane Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
apiVersion: pkg.crossplane.io/v1beta1
kind: DeploymentRuntimeConfig
metadata:
name: ctp-mcp
spec:
serviceAccountTemplate:
metadata:
# We need to provide additional permissions to the function. In order to
# do that we create a deterministic ServiceAccount name.
name: function-pod-analyzer
deploymentTemplate:
spec:
selector: {}
template:
spec:
containers:
- name: package-runtime
args:
- --debug
# Fine for local development (using crossplane render). Not fine
# when integrated with Crossplane.
# - --insecure
env:
# Inform the function of the CTP1 MCP Server.
# transport: http-stream indicates that we'll communicate with the
# MCP server over StreamableHTTP.
- name: MCP_SERVER_TOOL_CTP1_TRANSPORT
value: http-stream
# baseURL indicates which address and endpoint to reach out to for
# tooling.
- name: MCP_SERVER_TOOL_CTP1_BASEURL
value: http://localhost:8080/mcp
- name: controlplane-mcp-server
image: xpkg.upbound.io/upbound/controlplane-mcp-server:v0.1.0
args:
- --debug
Required Permissions for the function:
---
# log-and-event-reader provides sufficient yet narrow scoped permissions for
# reading pod logs and events related to the pod.
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: log-and-event-reader
rules:
# controlplane-mcp-server needs get/list on pods, pods/log, and events
# in order to retrieve information for analysis.
- apiGroups:
- ""
resources:
- events
- pods
- pods/log
verbs:
- get
- list
---
# Bind the above ClusterRole to the function's service account.
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: log-and-event-reader
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: log-and-event-reader
subjects:
- kind: ServiceAccount
name: function-pod-analyzer
namespace: crossplane-system
Function Spec:
---
apiVersion: pkg.crossplane.io/v1beta1
kind: Function
metadata:
name: function-claude
spec:
package: xpkg.upbound.io/upbound/function-claude:v0.1.0
runtimeConfigRef:
name: ctp-mcp
Read the logs of the given container of the given Kubernetes pod in the given namespace.
Parameters:
Read the events of the given Kubernetes pod in the given namespace.
Parameters: