Feature Description
Feature Request: Native Model Context Protocol (MCP) Server Support
Summary
Add optional support for the Model Context Protocol (MCP) so AI assistants (ChatGPT, Claude Desktop, VS Code, Cursor, etc.) can securely interact with CheckCle using a standardized interface.
This would enable users to query their monitoring infrastructure, inspect incidents, and automate operational tasks directly from AI clients without requiring custom API wrappers.
Proposed Design
Implement an optional MCP server that reuses CheckCle's existing services/API layer.
Example tools could include:
Monitoring
list_monitorsget_monitorcreate_monitorupdate_monitordelete_monitor
Incidents
list_incidentsget_incidentacknowledge_incidentresolve_incident
Servers
list_serversget_serverget_server_metrics
Status Pages
list_status_pagesget_status_page
System
Benefits
- Standard AI integration using MCP
- No need for third-party wrappers
- Works with ChatGPT, Claude, VS Code, Cursor, and future MCP-compatible clients
- Enables AI-powered monitoring workflows
- Makes CheckCle more attractive for homelab and DevOps users
Implementation Notes
- Should be completely optional.
- Should reuse existing business logic rather than duplicate functionality.
- Authentication should use existing CheckCle authentication where possible.
- Transport could initially support stdio, with HTTP/SSE support considered later.
Example Use Cases
"Show me all unhealthy monitors."
"Why is Server A reporting high CPU usage?"
"List all active incidents."
"Acknowledge incident #42."
"Summarize everything unhealthy in my homelab."
I would be happy to work on implementing this feature if the maintainers think it would be a good fit for the project.
Motivation
Motivation
The MCP ecosystem is growing rapidly, and many self-hosted users are beginning to integrate their infrastructure with AI tooling.
While CheckCle already exposes an API, every AI integration currently requires writing and maintaining a custom wrapper.
Native MCP support would provide a standardized interface that works across multiple AI platforms.
Alternatives Considered
No response
Additional Context
No response
Checklist
Feature Description
Feature Request: Native Model Context Protocol (MCP) Server Support
Summary
Add optional support for the Model Context Protocol (MCP) so AI assistants (ChatGPT, Claude Desktop, VS Code, Cursor, etc.) can securely interact with CheckCle using a standardized interface.
This would enable users to query their monitoring infrastructure, inspect incidents, and automate operational tasks directly from AI clients without requiring custom API wrappers.
Proposed Design
Implement an optional MCP server that reuses CheckCle's existing services/API layer.
Example tools could include:
Monitoring
list_monitorsget_monitorcreate_monitorupdate_monitordelete_monitorIncidents
list_incidentsget_incidentacknowledge_incidentresolve_incidentServers
list_serversget_serverget_server_metricsStatus Pages
list_status_pagesget_status_pageSystem
healthversionBenefits
Implementation Notes
Example Use Cases
I would be happy to work on implementing this feature if the maintainers think it would be a good fit for the project.
Motivation
Motivation
The MCP ecosystem is growing rapidly, and many self-hosted users are beginning to integrate their infrastructure with AI tooling.
While CheckCle already exposes an API, every AI integration currently requires writing and maintaining a custom wrapper.
Native MCP support would provide a standardized interface that works across multiple AI platforms.
Alternatives Considered
No response
Additional Context
No response
Checklist