Peers, groups, policies and posture checks are all readable from one connection, so "why can this machine reach that one" can be traced across the objects that decide it without clicking through four screens.
A read-only window onto a NetBird network. It maps a selected set of NetBird API resources one-to-one onto tools, so what you can ask for is exactly what the API publishes. The author describes the project as still in development.
- Every peer on the network, and the ingress port allocations for a given peer
- The groups, and the access policies defined over them
- Posture checks, so the conditions a device has to meet are readable alongside the policies that reference them
- Networks and nameserver groups, for the routing and DNS side of the configuration
- Read access only — nothing here changes the network's configuration
- The API host is configurable, so a self-hosted NetBird works the same way as the managed one
A NetBird API token, supplied as NETBIRD_API_TOKEN. The API host defaults to api.netbird.io — point it at your own if you self-host. Install with Go, or through Smithery for a desktop client.
One command plus a key — go install github.com/aantti/mcp-netbird/cmd/mcp-netbird@latest, then supply credentials
