N9e MCP Server
Nightingale monitoring system data access for alert management and observability tasks.
Data last scanned today · Reviewed today
Overview
N9e MCP Server enables AI assistants to interface directly with the Nightingale monitoring ecosystem. By leveraging the Model Context Protocol, it allows users to manage alerts, browse monitored targets, and interact with incident response pipelines using natural language queries. The server supports integration with Nightingale v8.0.0+ and offers flexible deployment options, including standard stdio mode for local clients or HTTP mode for shared infrastructure. Users can configure fine-grained access using personal API tokens, with support for both per-user credentials and centralized shared configuration setups.
Our verdict
This server receives a high-risk rating with a security score of 27/100. The score is primarily impacted by the absence of a clear open-source license for the repository and the lack of editorial oversight regarding its security implementation. Given that it handles sensitive monitoring and alert credentials, it is recommended only for experienced teams who can independently audit the Go codebase before deployment.
- Supports Nightingale v8.0.0+ monitoring systems
- Zero direct dependencies reduce supply chain risk
- Provides documentation for both stdio and HTTP transport modes
- No license detected, creating legal ambiguity for use
- Community-maintained rather than officially managed by Nightingale
- Authentication methods have not yet undergone security review
Tools
| Tool | Description | Risk |
|---|---|---|
| list_active_alerts | Active firing alerts | low |
| get_active_alert | Active firing alerts | low |
| list_history_alerts | Historical alerts | low |
| get_history_alert | Historical alerts | low |
| list_alert_rules | Alert rule listing | low |
| get_alert_rule | Alert rule listing | low |
| create_alert_rule | CRUD on a single rule | medium |
| update_alert_rule | CRUD on a single rule | medium |
| import_alert_rules | Bulk import (n9e JSON or Prometheus YAML) | medium |
| import_prom_rules | Bulk import (n9e JSON or Prometheus YAML) | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Which versions of Nightingale are supported?
This MCP server is compatible with Nightingale version 8.0.0 and higher.
›What is the requirement for token-based authentication?
You must ensure that HTTP.TokenAuth is enabled in your Nightingale config.toml file, and then generate a token through the Personal Settings menu in the Nightingale web interface.
›How does the --shared flag impact configuration?
When the server is started with --shared=true, it enforces the use of the N9E_TOKEN and N9E_BASE_URL provided at startup, and ignores any authentication headers sent by the client.
›Can individual clients point to different Nightingale instances?
Yes, unless the server is started in shared mode, clients can override the default connection settings by sending X-User-Token and X-N9e-Base-Url headers in their configuration.
›How can I deploy this server for platforms requiring HTTP network calls?
You should use the provided Docker Compose solution in the repository, which includes an mcp-proxy bridge to convert the default stdio transport to an HTTP network protocol.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.