PlugWiki
nightingale logo

Nightingale MCP Server: Setup for Claude Code, Cursor and Other Apps

OfficialRemote

Lets Claude, Cursor and other assistants query alerts, metrics, logs and dashboards in your self-hosted Nightingale (n9e) monitoring system.

Nightingale (n9e) is a self-hosted alerting and monitoring tool, and it has its own built-in MCP server at /mcp, no separate process to run. Each tool call carries your personal token and runs through Nightingale's normal permission checks, so the assistant can only reach what your account can reach. Write tools (creating or changing rules, dashboards, users and more) are off by default; an admin has to turn them on in the server config.

Good for

  • SREs and on-call engineers who want an assistant to check firing alerts and metrics
  • Teams self-hosting Nightingale who want read-only access from Claude or Cursor by default

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install nightingale MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the nightingale MCP server to Claude Code. Run this command:
    
    claude mcp add --transport http nightingale http://<your-n9e-host>:17000/mcp --header "X-User-Token: <your-token>"
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires A running Nightingale (n9e) v8+ instance, HTTP.TokenAuth enabled, A personal token (Profile, Token management).

Replace the address with the one your client can reach and <your-token> with your personal token. The path is /mcp. Use HTTPS for remote connections. Nightingale documents the .mcp.json style config; the claude mcp add command is the standard Claude Code form for the same settings.

Built from the package data we hold. Not yet tested by us. Source.

Tools

  • Lists alerts firing right now

    Returns currently firing alert events, with filters for severity, time range and keyword.

    Try: “Which critical alerts are firing right now?”

    Read · list_active_alerts

  • Reads one firing alert in detail

    Returns full details of one active alert event.

    Try: “Show me the details of alert 1024.”

    Read · get_active_alert

  • Lists past alerts

    Returns historical alert events with filters.

    Try: “What alerts fired on the payments service last week?”

    Read · list_history_alerts

  • Lists alert rules for a team

    Returns the alert rules configured for a business group.

    Try: “List the alert rules for the infra team.”

    Read · list_alert_rules

  • Reads one alert rule

    Returns one alert rule's full definition.

    Try: “Show me the CPU usage alert rule.”

    Read · get_alert_rule

  • Creates a new alert rule

    Creates an alert rule in a business group from the full rule definition you give it. It only exists when the admin has turned on write tools.

    Try: “Create a rule that alerts when disk usage is above 90 percent.”

    Write · create_alert_rule

  • Changes an alert rule

    Updates an existing alert rule's definition.

    Try: “Lower the CPU alert threshold to 80 percent.”

    Write · update_alert_rule

  • Enables or disables alert rules

    Switches a batch of alert rules on or off.

    Try: “Disable the noisy disk space rule for now.”

    Write · toggle_alert_rules

  • Lists active silences

    Returns the alert mutes (silences) set for a business group.

    Try: “What alerts are currently muted?”

    Read · list_mutes

  • Mutes an alert

    Creates a silence rule for a time range or a recurring schedule.

    Try: “Mute alerts for the database server for the next 2 hours.”

    Write · create_mute

  • Lists dashboards

    Lists dashboards for one or more business groups.

    Try: “What dashboards do we have for the infra team?”

    Read · list_dashboards

  • Reads a dashboard's full layout

    Returns a dashboard's metadata and its complete panel configuration.

    Try: “Show me the panel setup of the API latency dashboard.”

    Read · get_dashboard_pure

Read from the source code

Permissions

low risk · 2 things to watch

Low risk

By default every tool only reads your Nightingale data; an admin must turn on write tools before anything can be created or changed. Each tool call carries your own account's permissions.

What it can do

Watch out for

  • It acts with your own account's permissions

    Every tool call carries your token, so the assistant can only see and do what your Nightingale account can. github.com

  • Writes are off until an admin turns them on

    By default every client only gets read tools. Enabling writes exposes about 32 create, update and toggle tools, including users, roles, password resets and data sources, with no per-call approval on the server. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyWrite tools are off by default (MCPEnableWriteTools = false in the [HTTP.A2A] config section). An admin can also list only specific toolsets with MCPToolsets.
Sign-in and keysA personal token tied to your Nightingale account, sent in the X-User-Token header, or an OAuth access token for clients set up that way.

Questions

Is this official?

Yes. It ships inside Nightingale's own n9e process at /mcp; a standalone version also exists for running MCP against a remote Nightingale instance.

Does it need an API key?

It needs a personal token from your Nightingale account, sent as a header, or an OAuth access token for clients set up for OAuth.

Can it change my alert rules?

Only if an admin has turned on write tools. By default every client can only read data.

What is the Nightingale MCP server URL?

Your own instance's address with /mcp at the end, for example http://your-n9e-host:17000/mcp. There is no shared hosted address.

Is this the full tool list?

No. The list on this page is a partial sample. The server registers about 74 tools across 13 toolsets, and an admin can also restrict which toolsets are exposed.

Does it need AI to work?

No. Alerting works without AI. External MCP clients bring their own model; Nightingale's separate built-in AI assistant uses whatever model endpoint you configure for it.

Information

updated Nov 2, 2026

Publisher
Official
Transport
Streamable HTTP
Auth
API key
License
Apache-2.0
Last commit
Oct 30, 2026
Open issues
232

WebsiteGitHubChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 2
  1. github.com · github.com
  2. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.