Netbird

Created By
aanttia year ago
Overview

what is Netbird?

Netbird is a Model Context Protocol (MCP) server designed for managing network peers in the Netbird ecosystem, derived from the MCP Server for Grafana.

how to use Netbird?

To use Netbird, you need to install the mcp-netbird binary, configure it with your Netbird API token, and set up the server configuration in your client configuration file.

key features of Netbird?

  • Lists Netbird peers with detailed information including connected status, location, system details, and group membership.
  • Configurable API endpoint for flexibility.
  • Secure token-based authentication for enhanced security.

use cases of Netbird?

  1. Managing and monitoring network peers in a Netbird environment.
  2. Integrating with other tools that require network peer information.
  3. Developing custom applications that utilize the Netbird API.

FAQ from Netbird?

  • What is the purpose of the Netbird MCP server?

The Netbird MCP server is used to manage and monitor network peers within the Netbird ecosystem.

  • How do I install the Netbird MCP server?

You can install it from source or directly from GitHub using Go.

  • Is there any support for contributions?

Yes! Contributions are welcome, and you can open issues or submit pull requests.

Server Config

{
  "mcpServers": {
    "netbird": {
      "command": "mcp-netbird",
      "args": [],
      "env": {
        "NETBIRD_API_TOKEN": "your-token-here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aantti
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago