UniFi Access MCP logo

UniFi Access MCP

Manage UniFi Access doors, credentials, policies, visitors, and events through MCP tools.

Install UniFi Access MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "unifi-access-mcp": {
      "command": "uvx",
      "args": [
        "unifi-network-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

UniFi Access MCP connects AI assistants and automation tools to Ubiquiti UniFi Access controllers through the Model Context Protocol. Its Access package exposes tools for managing doors, credentials, policies, visitors, and events, with 37 tools listed for the Access server. Use it when an MCP client needs to query or operate UniFi Access resources through standard tool discovery and calls. The server also provides a setup-status tool that explains missing controller tools and how to apply new configuration.

Use cases

  • Manage UniFi Access doors from an AI assistant.
  • Review visitor activity and Access events.
  • Update credentials and access policies.
  • Diagnose missing UniFi controller tools.
  • Connect Access workflows to an MCP-compatible automation client.

Key features

  • Door management
  • Credential management
  • Access policy management
  • Visitor and event workflows
  • Lazy or eager MCP tool discovery
  • Configuration status diagnostics

Tools1

What UniFi Access MCP lets your agent do. Expand a tool for its parameters.

Verified live~61 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 46d

What it can do

From the 1 tool this server returned when we ran it; 1 declare their own safety hints.

Read-only tools · 1
Network at startup2 connections
Files written at startupNone

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · unifi-network-mcp@latest (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars945Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Tools exposed1Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How UniFi Access MCP works

What UniFi Access MCP does

UniFi Access MCP gives MCP-compatible clients an interface for working with Ubiquiti UniFi Access controllers. The Access server covers five operational areas: doors, credentials, policies, visitors, and events. The project lists the Access package as unifi-access-mcp, with 37 tools in the Access server.

This is one component of a larger UniFi MCP collection that also includes separate Network and Protect servers. Choose the Access package when the agent workflow concerns entry control and visitor activity rather than network administration or camera operations.

How it works

The server follows the standard MCP model. Clients discover registered tools with tools/list and invoke them with tools/call. UniFi MCP supports a lazy discovery mode that initially exposes meta-tools and allows clients to find and invoke domain tools on demand; an eager mode can register selected domain tools directly for clients that prefer a complete tool list.

Tool responses can use adaptive content handling based on the MCP protocol version negotiated during initialization. The global content setting can be overridden for the Access server with UNIFI_ACCESS_MCP_CONTENT_MODE.

The unifi_setup_status tool is intended for configuration troubleshooting. Call it when controller tools are absent: it reports the reason they are unavailable, describes how to configure the server, and explains how to load the new settings.

Setup and configuration

Install the Access package from PyPI as unifi-access-mcp. The project targets Python 3.13 or newer. Configure the server with the settings required to connect it to the relevant UniFi deployment, then use unifi_setup_status when the expected controller tools have not appeared.

MCP HTTP transport is disabled by default. When enabled, the packages bind to loopback by default. The available transport settings include UNIFI_MCP_HTTP_ENABLED, UNIFI_MCP_HOST, UNIFI_MCP_HTTP_FORCE, UNIFI_MCP_ALLOWED_HOSTS, and UNIFI_MCP_ENABLE_DNS_REBINDING_PROTECTION. HTTP access is unauthenticated and intended for trusted local clients, so remote deployments should use an authenticated TLS proxy or the project's Cloud Relay rather than exposing the backend directly.

Tools and capabilities

The Access server is intended for workflows that need to:

  • Manage UniFi Access doors.
  • Work with access credentials.
  • Manage access policies.
  • Handle visitor information.
  • Inspect or manage Access events.
  • Diagnose missing controller tools with unifi_setup_status.

The repository also supports marketplace plugins for Claude Code and Codex. These plugins can package the corresponding Access MCP server with agent skills and guided setup.

Limitations and notes

UniFi Access is separate from the Network and Protect servers in this project. Installing or configuring one product server does not imply that the other products' tools are available.

HTTP transport should be treated as a trusted-local interface unless protected by an authenticated proxy or Cloud Relay. The default loopback binding reduces exposure for local deployments, while container configurations may use different internal binding and port settings.

Clients that require the full result in the MCP content field may need compatibility response mode. The global UNIFI_MCP_CONTENT_MODE setting accepts compat, compact, or adaptive, and the Access-specific variable can override it for this server.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about UniFi Access MCP

UniFi Access MCP is an MCP server that connects AI assistants and automation tools to Ubiquiti UniFi Access controllers. Its main tools manage doors, credentials, policies, visitors, and events, while `unifi_setup_status` helps diagnose missing controller tools and explains how to apply configuration changes.

Install the `unifi-access-mcp` package from PyPI and use Python 3.13 or newer. Configure it for the target UniFi deployment, then call `unifi_setup_status` if the controller tools do not appear.

Call `unifi_setup_status`. It reports why the controller tools are unavailable, provides configuration guidance, and explains how to load the new settings.

Yes, HTTP transport is supported but disabled by default. When enabled, it binds to loopback by default; use an authenticated TLS proxy or Cloud Relay for remote access instead of exposing the unauthenticated backend directly.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUniFi Access MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/unifi-access-mcp?style=directory)](https://allmcps.com/mcp/unifi-access-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/unifi-access-mcp"><img src="https://allmcps.com/api/badge/unifi-access-mcp?style=directory" alt="UniFi Access MCP on AllMCPs" /></a>