← Back to directory
U

UniFi Access MCP

Community
Manage UniFi Access through MCP.
GitHub source repository ↗
★ 749 Stars Category · Other Very popular Source revision eb06c7141030
61FMRS · C
Reliability
9/20
Security and permissions
14/20
Maintenance
13/20
Documentation
12/20
Setup experience
13/20

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.

Read the FMRS scoring method →

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.

Tools

The tool list has not been reviewed yet.

Setup

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"}}}}

Fit and risk

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.

Troubleshooting

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

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 DesktopFull support
CodexFull support
OpenClawFull support

More servers from this repository