MCP Netbird MCP Server

Mcp netbird mcp server connects MCP Netbird to AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for Netbird.

What MCP Netbird does

A Model Context Protocol (MCP) server for Netbird.

Key capabilities

• Uses Netbird API to access configuration and status
• Configurable API endpoint
• Secure token-based authentication for Netbird API

Tools it exposes

Once connected, the assistant can call these 11 tools directly:

• list_netbird_peers — All peers
• list_netbird_port_allocations — All ingress ports for peerId
• list_netbird_groups — All groups
• list_netbird_policies — All policies
• list_netbird_posture_checks — All posture checks
• list_netbird_networks — All networks
• list_netbird_nameservers — All nameserver groups
• Tools — The Tools tool exposed by this server
• Debugging — The MCP Inspector is an interactive developer tool for testing and debugging MCP servers. Read more about it
• Testing — The Testing tool exposed by this server
• Linting — The Linting tool exposed by this server

Installing the mcp netbird mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 2 environment variables: NETBIRD_API_TOKEN, NETBIRD_HOST. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Netbird sits in that group, and the shape of its toolset — list_netbird_peers, list_netbird_port_allocations, list_netbird_groups among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 11 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use MCP Netbird.
• Maintained by aantti, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp netbird mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.