Nightingale MCP Server
The official Nightingale MCP server: an agent reads alerts and metrics and manages alert rules and dashboards of the monitoring system
- 42 ★ on the repository
- Last commit
Broad access
Why this level
- A Nightingale token gives the agent the rights of its owner, including alert rules, notification channels and dashboards
- `create_user`, `reset_user_password` and `bind_role_operations` change accounts and access rights
- Notification mutes and disabled rules can silence real alerts
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/nightingale-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A Nightingale token gives the agent the rights of its owner, including alert rules, notification channels and dashboards
- `create_user`, `reset_user_password` and `bind_role_operations` change accounts and access rights
- Notification mutes and disabled rules can silence real alerts
This is third-party code. Review the repository files before installing.
What it does
The MCP server for the Nightingale (n9e) monitoring system opens its API to an agent. The agent reads active and historical alerts, alert rules, monitored hosts, data sources, users and roles, runs PromQL queries and searches Loki, Elasticsearch and OpenSearch logs. Write tools create and update alert rules, including bulk import of Prometheus rules, and manage notification mutes, notification rules and channels, dashboards, users and roles. The `--read-only` flag turns writing off, and the `N9E_TOOLSETS` variable narrows the toolset. The server runs over stdio or HTTP. In HTTP mode one server can serve several users: the token and address come from the `X-User-Token` and `X-N9e-Base-Url` headers, while the `--shared` flag pins a single set of credentials.
Who it is for. SREs and on-call engineers whose monitoring runs on Nightingale 8 or newer.
Good fit when
- Alerts fired overnight, and the agent gathers active alerts for a business group and pulls up the related rules
- You need a PromQL query over several hours, with the step chosen so the answer fits into 1000 points
- Prometheus rules in YAML are moved to Nightingale by bulk import
- A notification mute is needed for a group of hosts during maintenance
- Dify or FastGPT has to reach Nightingale over HTTP through the Docker Compose setup from the repository
Not a fit when
- Nightingale is older than 8.0.0: compatibility is declared from that version
- Monitoring runs on Zabbix or Datadog: the server talks only to the Nightingale API
- The agent must not change rules and roles but the token has wide rights: without the `--read-only` flag the write tools stay available
Example request
Show the active alerts from the last hour and the rules that fired them.MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
N9E_TOKENrequired, secret- A Nightingale API token from personal settings.
N9E_BASE_URLrequired- The Nightingale server address, for example `http://your-n9e-server:17000`.
N9E_TOOLSETS- A list of toolsets to keep.
Limitations
A Nightingale API token is required: `HTTP.TokenAuth` is enabled in `config.toml` and the token is created in personal settings. Compatibility is declared with Nightingale 8.0.0 and newer. A log query rejects a time range longer than 7 days and returns 200 records by default. Write tools are available by default and can be turned off with the `--read-only` flag. In HTTP mode without `--shared` the token and address can be left out at startup: each client sends its own in headers.
How to disable. Remove the `nightingale` block from `~/.cursor/mcp.json`. To keep the server without write access, add `--read-only` to the launch arguments.
FAQ
How do I connect Nightingale MCP Server to Cursor?
Add a `nightingale` server to `~/.cursor/mcp.json` with the command `npx` and the arguments `-y`, `@n9e/n9e-mcp-server`, `stdio`. Put `N9E_TOKEN` and `N9E_BASE_URL` into the `env` block and restart Cursor.
Where do I get the token for Nightingale MCP Server?
Enable `HTTP.TokenAuth` in the Nightingale `config.toml`, sign in to the web interface and create a token under Personal Settings, Profile, Token Management. The token's permissions set what the agent can do.
How do I stop the agent from changing rules and dashboards?
Start the server with the `--read-only` flag: the create, update, import and toggle tools are not registered. Reading alerts, rules, metrics and logs remains.
How do I run the server over HTTP for several users?
With `n9e-mcp-server http --listen :8080`. Without `--shared` each client sends its own token and address in the `X-User-Token` and `X-N9e-Base-Url` headers. With `--shared` the server takes `N9E_TOKEN` and `N9E_BASE_URL` from startup and ignores client headers.
Which toolsets does the server have?
`alerts`, `targets`, `datasource`, `mutes`, `busi_groups`, `notify_rules`, `alert_subscribes`, `event_pipelines`, `users`, `metrics`, `logs`, `dashboards` and `roles`. A subset can be kept with the `N9E_TOOLSETS` variable.
Discussion
No questions or reviews yet.
Related
MCP serversThe official Prometheus MCP server: PromQL queries, metrics, rules and alerts plus built-in runbooks for troubleshooting.
An MCP server for Prometheus: the agent runs PromQL queries, discovers metrics and checks scrape targets
Grafana MCP Server
Grafana MCP server
Grafana's official MCP server: dashboards, Prometheus and Loki queries, alerts and incidents straight from the agent
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
Datadog MCP Server (winor30)
Datadog MCP Server
Independent Datadog MCP server: an agent reads incidents, monitors, logs, metrics, traces and RUM and schedules downtimes.
Zabbix MCP Server (mpeirone)
Zabbix MCP Server
The MCP server exposes Zabbix API calls, documentation and method discovery with read-only and method-filter controls.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Nightingale MCP Server (this card) | yes | API key | 42 | |
| Zabbix MCP Server (mpeirone) | no | API key | 260 | a server for Zabbix that does not work with Nightingale |
| Grafana MCP Server | yes | API key | 3,644 | a server for Grafana and its data sources, with no access to Nightingale alert rules |
| Datadog MCP Server | yes | OAuth | 47 | Datadog cloud monitoring, a different service and API |
README in short
The repository starts with compatibility and use cases, then walks through the steps: token, client setup, HTTP mode and Docker for platforms such as Dify. After that come the tools by toolset, split into read and write.