UniFi Access MCP

Community

Manage UniFi Access through MCP.

How to install ↓ Compare GitHub source repository ↗

Category: Other #64 of 230
Stars: ★ 921 Very popular
Transport: stdio (local process)
Runtime: Python 3.13+
Credentials: API key / credential required
License: MIT
Last commit: 3 days ago

61FMRS · C

The source identifies version 0.5.6, the unifi-access-mcp package, the MIT license, and 36 Access tools, but does not provide individual tool identifiers.

Strongest · Security and permissions 14/20 Weakest · Reliability 9/20

Reliability

9/20

Security and permissions

14/20

Maintenance

13/20

Documentation

12/20

Setup experience

13/20

Why each score

Reliability 9/20: The manifest declares a PyPI package using stdio, and the root README labels Access Stable with 36 tools, making the startup path plausible statically. However, the provided material contains no source for apps/access/server.json, tool definitions, error-handling evidence, CI, or server-specific tests, so initialization, tool-list consistency, and failure behavior cannot be verified; the static calibration therefore requires a deduction.
Security and permissions 14/20: The evidence shows secret-marked credential variables, default redaction of sensitive fields, and preview-then-confirm behavior for mutations; the stated boundary is a local UniFi controller. Deductions apply because UNIFI_VERIFY_SSL defaults to false, the server requires administrator credentials, the API key is experimental, and no Access-specific evidence establishes least-privilege permissions, auditing, or detailed network data boundaries.
Maintenance 13/20: The repository is not archived, uses the MIT license, reports server version 0.5.6, labels Access Stable, and exposes an issue count. These support a baseline case for ongoing maintenance. The supplied material does not establish commit cadence, release history, dependency-update practice, vulnerability response, or Access-specific ownership evidence, so the score is well below full marks.
Documentation 12/20: The root README supplies server scope, an Access capability summary, installation commands, client configuration examples, account requirements, environment variables, redaction behavior, and mutation confirmation guidance. Points are deducted because the detailed Access documentation is only linked, so tool parameters, limits, troubleshooting, and implementation behavior are not reviewable from the supplied material; information about sibling servers and components cannot be attributed to Access.
Setup experience 13/20: The material provides a uvx launch command plus configuration examples for Claude Desktop, Codex, and OpenClaw, and identifies the required local account and environment variables. Deductions reflect the need to manually prepare an account and credentials, the default disabled SSL verification, and the absence of platform-compatibility, dependency-failure, or Access-specific installation-verification evidence; under static calibration the score remains at or below 15.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

Home-automation or small-organization administrators using UniFi Access.
Users who need AI-assisted access to a local UniFi Access controller.
Deployments able to maintain a local UniFi administrator or service account.

Not for

Users who only have a Ubiquiti SSO cloud account and cannot provide a local controller account.
Users needing Network or Protect functionality; those are separate servers in the repository.
Environments where AI workflows must not access door, credential, or visitor data.

Required permissions

Requires the UniFi controller IP address or hostname.
Requires a local UniFi administrator or service-account username and password.
The account should have permissions for the required access-management operations.
A UniFi API key may be used optionally; the source labels it experimental.

Risks and side effects

Door, credential, and visitor operations can affect real physical access.
Controller credentials and API keys are sensitive and must be protected.
UNIFI_VERIFY_SSL defaults to false, which can reduce TLS certificate-validation protection.
Incorrect permissions or requests may cause unintended access-configuration changes.

Setup

Before you start

Runtime：Python 3.13+

UNIFI_ACCESS_HOST required IP or hostname of the UniFi Access controller; use the local controller address.

UNIFI_ACCESS_USERNAME requiredsecret Local admin/service account username; do not use a Ubiquiti SSO cloud account.

UNIFI_ACCESS_PASSWORD requiredsecret Password for that local account.

UNIFI_ACCESS_API_KEY optionalsecret Optional UniFi API key for selected/experimental capabilities; generate it on the controller.

UNIFI_USERNAME optionalsecret Shared fallback variable: local admin username.

UNIFI_PASSWORD optionalsecret Shared fallback variable: local admin password.

UNIFI_API_KEY optionalsecret Shared fallback variable: optional API key.

Other optional settings (9)

UNIFI_ACCESS_PORT optional Controller HTTPS port, defaults to 443.

UNIFI_ACCESS_VERIFY_SSL optional Whether to verify SSL certificates, defaults to false.

UNIFI_HOST optional Shared fallback variable: controller IP or hostname (the Access server prefers UNIFI_ACCESS_*).

UNIFI_PORT optional Shared fallback variable: controller HTTPS port.

UNIFI_VERIFY_SSL optional Shared fallback variable: SSL verification toggle.

UNIFI_ACCESS_MCP_CONTENT_MODE optional Per-server override for response content mode (compat or compact).

UNIFI_MCP_CONTENT_MODE optional Global content mode; compat keeps full JSON in content, compact uses concise text plus structuredContent.

UNIFI_ACCESS_REDACT_SENSITIVE_FIELDS optional Set to false to disable redaction of sensitive fields (e.g. credential tokens/PINs) for this server.

UNIFI_REDACT_SENSITIVE_FIELDS optional Global sensitive-field redaction toggle, on by default.

Run unifi-access-mcp@latest with uvx and configure UNIFI_HOST, UNIFI_USERNAME, and UNIFI_PASSWORD. UNIFI_PORT defaults to 443 and UNIFI_VERIFY_SSL defaults to false; UNIFI_API_KEY is optional. Use a local administrator or service account rather than a Ubiquiti SSO cloud account. The server also supports corresponding UNIFI_ACCESS_* variables, which take priority.

claude_desktop_config.json

{"mcpServers":{"unifi-access":{"command":"uvx","args":["unifi-access-mcp@latest"],"env":{"UNIFI_ACCESS_HOST":"192.168.1.1","UNIFI_ACCESS_USERNAME":"admin","UNIFI_ACCESS_PASSWORD":"your-password"}}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "unifi-access": {
      "command": "uvx",
      "args": [
        "unifi-access-mcp@latest"
      ],
      "env": {
        "UNIFI_ACCESS_HOST": "192.168.1.1",
        "UNIFI_ACCESS_USERNAME": "admin",
        "UNIFI_ACCESS_PASSWORD": "your-password"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add unifi-access -e UNIFI_ACCESS_HOST=192.168.1.1 -e UNIFI_ACCESS_USERNAME=admin -e UNIFI_ACCESS_PASSWORD=your-password -- uvx unifi-access-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Run uvx unifi-access-mcp@latest with UNIFI_ACCESS_HOST/USERNAME/PASSWORD set, then in your MCP client run tools/list to confirm the UniFi Access tools are registered, and ask "Who badged into the office today?" to verify it returns real access events.

Troubleshooting

Verify that UNIFI_HOST points to the correct UniFi controller and check the HTTPS port; the default is 443.
Confirm that a local administrator or service account is being used instead of a Ubiquiti SSO cloud account.
Check the username and password and verify that the account has the required permissions.
When using server-specific configuration, verify the UNIFI_ACCESS_* variable names and values.
Check SSL-verification settings, especially when using a self-signed certificate.
Confirm that the unifi-access-mcp@latest PyPI package is installed and running.

Things to try

Once connected, you can ask your AI assistant things like:

Who badged into the office today? Show me a timeline of all door access events
Create a visitor pass for John Smith with access to the main entrance tomorrow 9-5
List all doors and credentials configured in UniFi Access
Show me access events from today and summarize any unusual activity

Use cases

Query door-access events and visitor activity.

Manage doors, credentials, and access policies.

Create or manage visitor access arrangements.

Let an AI assistant help administer UniFi Access.

Supported clients

Claude Desktop

Codex

OpenClaw

Listed from the project's documentation, not tested by this site.

Overview

UniFi Access MCP is a stdio MCP server for managing UniFi Access doors, credentials, access policies, visitors, and events through a UniFi controller. It is maintained as part of an independent open-source project and is not an official Ubiquiti server.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 517 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.6k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 583 · Tools 14 Compare with this →

Compare with other MCP servers

More servers from this repository

Source revision fbd083c62ec8 Data synced 2026-10-19 Read the FMRS scoring method