Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_TLS_MODENonone, https, or mtls.none
MCP_AUTH_MODENonone, bearer, or oauth. Unset resolves to bearer when MCP_BEARER_TOKEN is set, else none.unset
UNIFI_API_KEYNoSingle API key shorthand. Required if UNIFI_API_KEYS is not set.
UNIFI_API_KEYSNoJSON list of key configs for multi-console MSP setups.[]
MCP_TLS_KEYFILENoServer private key path. Required for https/mtls.
UNIFI_LOG_LEVELNoLogging verbosity. Accepts DEBUG, INFO, WARNING, ERROR, CRITICAL.INFO
MCP_BEARER_TOKENNoShared secret for bearer mode.
MCP_OAUTH_ISSUERNoOAuth issuer URL. Required for oauth.
MCP_TLS_CA_CERTSNoClient CA bundle for verifying client certs. Required for mtls.
MCP_TLS_CERTFILENoServer certificate path. Required for https/mtls.
FASTMCP_TRANSPORTNoSets the communication protocol between the MCP server and clients.streamable-http
MCP_TLS_CERT_REQSNoClient-cert verification level for mtls: none, optional, or required.
MCP_OAUTH_AUDIENCENoExpected token audience. Required for oauth.
MCP_OAUTH_BASE_URLNoPublic base URL of this resource server. Required for oauth.
MCP_OAUTH_JWKS_URINoJWKS URI for signature verification. Required for oauth.
UNIFI_API_BASE_URLNoUniFi Site Manager API base URL.https://api.ui.com
MCP_OAUTH_ALGORITHMNoJWT signing algorithm to accept.RS256
MCP_TLS_KEY_PASSWORDNoPassword for an encrypted private key. Optional.
UNIFI_CACHE_MAX_HOSTSNoMax entries in the hosts TTLCache.512
UNIFI_CACHE_MAX_SITESNoMax entries in the per-console sites TTLCache.2048
UNIFI_MAX_CONCURRENCYNoMax concurrent outbound requests to api.ui.com.10
UNIFI_CACHE_TTL_SECONDSNoTTL for host/site registry cache (seconds).900
UNIFI_PAGINATE_MAX_PAGESNoHard cap on pages drained per call. Default is unlimited.None
MCP_OAUTH_REQUIRED_SCOPESNoComma-separated scopes a token must carry.
UNIFI_ENABLE_MOBILITY_WRITENoEnable guarded Mobility write tools. Fail-closed: default OFF.false
UNIFI_ENABLE_CONNECTOR_WRITENoEnable the mutating generic connector relay. Fail-closed: default OFF.false
UNIFI_REQUEST_TIMEOUT_SECONDSNoHTTP request timeout in seconds.30
MCP_OAUTH_AUTHORIZATION_SERVERSNoComma-separated authorization-server URLs. Defaults to [MCP_OAUTH_ISSUER].
UNIFI_PROTECT_MUTATIONS_ENABLEDNoDeployment-level kill switch for all Protect mutation and physical-action tools. Default ON.true
UNIFI_ENABLE_CARRIER_FABRIC_WRITENoEnable guarded Carrier / ISP Fabric write tools. Fail-closed: default OFF.false

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_toolsA

Find enabled tools by intent, ranked over names, descriptions and parameter schemas.

Default returns ten matches. Choose any positive limit, or null for every match; no tool or search result is hard-capped. Empty query browses tools. Use describe_tool for the exact schema, then call_read_tool or call_write_tool.

Args: query: Natural language intent, for example "camera recordings"; empty browses all tools. family: Optional exact family slug from list_tool_families, for example "protect". writes: Optional filter: true for mutations, false for reads, null for both. limit: Number of results (default 10); any positive integer or null for every match. Enabled families (tool counts): carrier: 11; clients: 14; connector: 5; devices: 34; firewall: 32; hotspot: 4; innerspace: 32; mobility: 8; network: 347; protect: 227; site_manager: 19; statistics: 14; vpn: 39.

describe_toolA

Return the complete enabled tool schema, identical to its full-mode tools/list entry.

Args: name: Exact enabled tool name from search_tools, for example "get_acl_rule_ordering".

call_read_toolA

Execute a read tool with its original validation, guards, audit and result format.

Refuses write calls, including state-changing routes of the mixed GET relay. Describe the target first; its schema and permissions apply. Read-only mode and secret scrubbing are preserved.

Args: name: Exact enabled read tool name, for example "get_acl_rule_ordering". arguments: Target schema arguments, for example {"host": "console", "site": "default"}.

call_write_toolA

Execute a tool that may mutate live configuration through registered dispatch.

Describe the target first. Target validation, per-area opt-outs, UNIFI_READ_ONLY, OAuth permissions, dry-run, audit and secret scrubbing match a direct call.

Args: name: Exact enabled tool name, for example "set_firewall_policy_ordering". arguments: Target schema arguments from describe_tool; for example {"host": "console", "site": "default"} plus the target's required fields.

list_tool_familiesA

List enabled families and counts; use their slugs as search_tools family filters.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation4/5

The five meta-tools follow a clear discover→describe→call workflow: search_tools finds tools, describe_tool returns schemas, call_read_tool/call_write_tool execute, and list_tool_families exposes family slugs. There is minor overlap because search_tools already advertises enabled families and counts, making list_tool_families somewhat redundant; read/write separation is clear but an agent must classify a target as read or write before calling.

Naming Consistency5/5

All names are snake_case verb_noun constructions (search_tools, describe_tool, list_tool_families, call_read_tool, call_write_tool). The call_*_tool variants are slightly compound but follow the same verb-first convention consistently.

Tool Count5/5

Five tools is a compact, well-scoped surface for a gateway that fronts hundreds of underlying UniFi tools. Each meta-tool earns its place by covering discovery, schema inspection, read execution, write execution, and family listing.

Completeness5/5

The meta-tool set covers the full lifecycle needed for the catalog: browse/search, list families, inspect schemas, and execute both read and write tools. No obvious operation is missing for a fabric/gateway server; edge cases like mixed GET relays are explicitly handled by the read/write split.

Maintenance

ActivityMaintained
ResponsivenessSlow