Karma MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KARMA_URL | Yes | The URL of your Karma instance |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_karmaB | Check connection to Karma server |
| list_alertsB | List all active alerts in Karma |
| get_alerts_summaryB | Get a summary of alerts grouped by severity and state |
| list_clustersB | List all available Kubernetes clusters in Karma |
| list_alerts_by_clusterB | List alerts filtered by specific cluster Args: cluster_name: Name of the cluster to filter by (e.g., 'teddy-prod', 'edge-prod') |
| get_alert_detailsC | Get detailed information about a specific alert Args: alert_name: Name of the alert to get details for |
| list_active_alertsB | List only active (non-suppressed) alerts |
| list_suppressed_alertsB | List only suppressed alerts |
| get_alerts_by_stateB | Get alerts filtered by state (active, suppressed, or all) |
| get_alert_details_multi_clusterB | Get detailed information about a specific alert across multiple clusters Args: alert_name: Name of the alert to search for (e.g., 'KubePodCrashLooping') cluster_filter: Optional cluster name filter. If empty, searches all clusters. |
| search_alerts_by_containerB | Search for alerts by container name across multiple clusters Args: container_name: Name of the container to search for cluster_filter: Optional cluster name filter (e.g., 'teddy-prod', 'edge-prod'). If empty, searches all clusters. |
| list_silencesC | List all active silences across clusters or for a specific cluster Args: cluster: Optional cluster name to filter silences (e.g., 'teddy-prod') Returns: Formatted list of active silences with details |
| create_silenceC | Create a new silence for specific alerts Args: cluster: Target cluster name (e.g., 'teddy-prod') alertname: Name of the alert to silence duration: Duration of silence (e.g., '2h', '30m', '1d') comment: Comment explaining why the alert is being silenced matchers: Additional matchers in format 'key=value,key2=value2' (optional) Returns: Silence creation result with silence ID |
| delete_silenceC | Delete (expire) an existing silence Args: silence_id: ID of the silence to delete cluster: Cluster where the silence exists Returns: Deletion result |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_alert_analysis_prompt | Comprehensive prompt for alert analysis and troubleshooting |
| get_incident_response_prompt | Guidelines for incident response and escalation |
| get_kubernetes_context_prompt | Kubernetes-specific context for alert interpretation |
| get_business_impact_prompt | Business impact assessment guidelines for alert prioritization |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/driosalido/mcp-karma'
If you have feedback or need assistance with the MCP directory API, please join our Discord server