mcp-server-ntopng

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is mcp-server-ntopng?

The mcp-server-ntopng is an implementation of a Model Context Protocol (MCP) server for NTOPNG, enabling AI agents to query network monitoring data using the NTOPNG database.

How to use mcp-server-ntopng?

To use the mcp-server-ntopng, configure the server settings in the Claude Desktop application, ensuring that the NTOPNG host and database credentials are correctly set. Then, run the server using the provided commands.

Key features of mcp-server-ntopng?

  • Integration with NTOPNG for network monitoring.
  • Various tools for fetching network data, including interface IDs, host locations, and alert statistics.
  • Support for ClickHouse as a database for storing historical flows and alerts.

Use cases of mcp-server-ntopng?

  1. Monitoring network traffic and identifying top talkers.
  2. Fetching geographical data for network hosts.
  3. Analyzing alert statistics for network performance.

FAQ from mcp-server-ntopng?

  • What is NTOPNG?

NTOPNG is a network traffic analysis tool that provides insights into network performance and usage.

  • How do I configure the server?

Configuration involves editing the Claude Desktop configuration file to include the necessary NTOPNG connection details.

  • Is there support for other databases?

Currently, the server is designed to work with ClickHouse for NTOPNG.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago