Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Connects Claude to OpenNMS, allowing plain language interaction with alarms, nodes, events, asset records, categories, and service collection.

README.md

opennms-mcp

An MCP (Model Context Protocol) server that connects Claude to OpenNMS. Ask Claude to list alarms, inspect nodes, send events, update asset records, manage categories, and control service collection — all in plain language.

Prerequisites

  • Node.js 22+
  • An OpenNMS instance reachable over HTTP/HTTPS
  • A user account with API access (admin or a read/write role)

Installation

git clone https://github.com/c-perronnet/opennms-mcp.git
cd opennms-mcp
npm install
npm run build

Configuration

Create a JSON file with your OpenNMS credentials. Two auth formats are supported:

Basic auth (opennms/myserver.json): ``json { "url": "https://opennms.example.com", "username": "admin", "password": "secret" } ``

Token auth (opennms/myserver.json): ``json { "url": "https://opennms.example.com", "token": "your-api-token" } ``

Add "insecure": true to either format to skip TLS certificate validation (useful for self-signed certs).

Store config files in the opennms/ directory — it is git-ignored so credentials are never committed.

Connecting to Claude Desktop

Add the server to your claude_desktop_config.json:

{
  "mcpServers": {
    "opennms": {
      "command": "node",
      "args": ["/absolute/path/to/opennms-mcp/dist/index.js"],
      "env": {
        "OPENNMS_CONFIG": "/absolute/path/to/opennms-mcp/opennms/myserver.json"
      }
    }
  }
}

Alternatively, pass the config path as a positional argument:

{
  "mcpServers": {
    "opennms": {
      "command": "node",
      "args": [
        "/absolute/path/to/opennms-mcp/dist/index.js",
        "/absolute/path/to/opennms-mcp/opennms/myserver.json"
      ]
    }
  }
}

Connecting to Claude Code

Claude Code reads MCP server config from ~/.claude/claude_mcp_settings.json. Add the server there:

{
  "mcpServers": {
    "opennms": {
      "command": "node",
      "args": ["/absolute/path/to/opennms-mcp/dist/index.js"],
      "env": {
        "OPENNMS_CONFIG": "/absolute/path/to/opennms-mcp/opennms/myserver.json"
      }
    }
  }
}

Or configure it via the CLI:

claude mcp add opennms \
  -e OPENNMS_CONFIG=/absolute/path/to/opennms-mcp/opennms/myserver.json \
  -- node /absolute/path/to/opennms-mcp/dist/index.js

Verify the server is loaded with /mcp in the Claude Code prompt. The tools listed below will then be available in any conversation.

Available tools

Connectivity

| Tool | Description | |------|-------------| | server_info | Verify connectivity and return OpenNMS version |

Alarms

| Tool | Description | |------|-------------| | list_alarms | List alarms, optionally filtered by FIQL expression | | get_alarm | Get full details for an alarm by ID | | acknowledge_alarm | Acknowledge an alarm | | modify_alarm | Unacknowledge, clear, or escalate an alarm |

Nodes

| Tool | Description | |------|-------------| | list_nodes | List nodes, optionally filtered by FIQL expression | | get_node | Get full node details (accepts numeric ID or foreignSource:foreignId) | | get_node_ip_interfaces | List IP interfaces for a node | | get_node_snmp_interfaces | List SNMP interfaces for a node | | get_node_outages | List outages for a node | | rescan_node | Trigger a capability rescan for a node |

Events

| Tool | Description | |------|-------------| | list_events | List events, optionally filtered by FIQL expression | | get_event | Get full details for an event by ID | | send_event | Send a custom event to the OpenNMS event bus |

Asset records

| Tool | Description | |------|-------------| | get_node_asset_record | Get the asset record for a node | | update_node_asset_record | Update one or more asset fields for a node |

Categories

| Tool | Description | |------|-------------| | list_categories | List all categories defined in OpenNMS | | get_node_categories | List categories assigned to a node | | add_category_to_node | Assign a category to a node | | remove_category_from_node | Remove a category from a node |

Collection / polling

| Tool | Description | |------|-------------| | list_node_services | List monitored services on a node's IP interface | | enable_service_collection | Enable collection for a service (set to Active) | | disable_service_collection | Disable collection for a service (set to Forced Unmanaged) |

FIQL filtering

Several list tools accept a filter parameter using FIQL syntax:

| Operator | Meaning | |----------|---------| | == | equals | | != | not equals | | =lt= | less than | | =gt= | greater than | | ; | AND | | , | OR |

Examples:

  • severity==CRITICAL — critical alarms only
  • node.label==web* — nodes whose label starts with "web"
  • severity==MAJOR,severity==CRITICAL — major or critical alarms
  • category.name==Routers — nodes in the Routers category

Development

npm run dev    # watch mode — recompiles on file changes
npm run build  # one-shot compile to dist/
npm start      # run compiled server (requires OPENNMS_CONFIG)

License

MIT

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Other servers.