unifi-rmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFI_URL | Yes | Controller base URL, e.g. https://unifi.local. | unset |
| UNIFI_SITE | No | UniFi site name. | default |
| UNIFI_LEGACY | No | Legacy controller mode without /proxy/network prefix. | false |
| UNIFI_NOAUTH | No | Trust an upstream gateway to enforce auth. | false |
| UNIFI_API_KEY | Yes | API key for the X-API-KEY header. | unset |
| UNIFI_SITE_ID | No | Official API site UUID used by live tests and explicit generated calls. | unset |
| UNIFI_MCP_HOME | No | Appdata dir override; read by setup only. | ~/.unifi-rmcp |
| UNIFI_MCP_HOST | No | HTTP bind host. | 0.0.0.0 |
| UNIFI_MCP_PORT | No | HTTP bind port. | 40030 |
| UNIFI_MCP_TOKEN | No | Static bearer token for HTTP MCP. | unset |
| UNIFI_MCP_NO_AUTH | No | Disable auth only for loopback development. | false |
| UNIFI_MCP_AUTH_MODE | No | bearer or oauth. | bearer |
| UNIFI_MCP_PUBLIC_URL | No | Public URL for OAuth metadata. | unset |
| UNIFI_SKIP_TLS_VERIFY | No | Skip TLS certificate verification for self-signed controllers. | true |
| UNIFI_MCP_ALLOWED_HOSTS | No | Comma-separated Host header allowlist. | empty |
| UNIFI_MCP_AUTH_KEY_PATH | No | OAuth JWT signing key path. | /data/auth-jwt.pem |
| UNIFI_MCP_ALLOWED_ORIGINS | No | Comma-separated CORS Origin allowlist. | empty |
| UNIFI_MCP_AUTH_ADMIN_EMAIL | No | Admin email for OAuth bootstrap. | unset |
| UNIFI_MCP_AUTH_SQLITE_PATH | No | OAuth state database path. | /data/auth.db |
| UNIFI_MCP_GOOGLE_CLIENT_ID | No | Google OAuth client ID. | unset |
| UNIFI_MCP_DISABLE_HTTP_AUTH | No | Compatibility alias for UNIFI_MCP_NO_AUTH. | false |
| UNIFI_MCP_GOOGLE_CLIENT_SECRET | No | Google OAuth client secret. | unset |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dinglebear-ai/runifi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server