Skip to main content
Glama
shark-fi

unifi-talk-mcp

by shark-fi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TALK_CA_CERTNoPath to the console's CA certificate (PEM)
TALK_BASE_URLYesConsole address, e.g. https://192.168.1.1
TALK_PASSWORDYesIts password
TALK_USERNAMEYesLocal UniFi OS account
TALK_TIMEOUT_MSNoPer-request timeout30000
TALK_ALLOW_WRITESNoEnable talk_invokefalse
TALK_INSECURE_TLSNoSkip TLS verification. Last resortfalse

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
talk_statusA

Talk version and region, console summary, and service health. A good first call.

talk_list_callsB

Call history with caller ID, direction, status, and voicemail data. Paginated.

talk_get_callA

Event timeline and transcription (if enabled) for one call, by the uuid from talk_list_calls.

talk_list_devicesB

Talk desk phones and softphone apps with user, extension, status, SIP registration, last seen, IP, and firmware. A compact view of the devices endpoint; filter by status or kind.

talk_list_endpointsA

Catalog of known UniFi Talk API endpoints (users, numbers, devices, routing, voicemail, billing, and more) with their parameters. Use it to find an endpoint id for talk_get or talk_invoke.

talk_getB

Call any read-only Talk endpoint by id. See talk_list_endpoints for descriptions and parameters.

talk_invokeA

Call a Talk endpoint that changes or deletes data. Disabled unless the server runs with TALK_ALLOW_WRITES=true. Confirm with the user before calling. See talk_list_endpoints for body shapes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct purposes: status, write operations, call history, call detail, devices, endpoint catalog, and generic reads. Slight overlap exists between talk_get_call (specialized call timeline) and talk_get (generic read by endpoint id), but descriptions clarify the intended use.

Naming Consistency4/5

All tools share the talk_ prefix and mostly follow verb_noun (talk_list_calls, talk_get_call, talk_list_devices). talk_status and talk_invoke deviate slightly from the pattern, but the naming remains predictable and readable.

Tool Count5/5

Seven tools is well-scoped for a UniFi Talk integration: a status check, a write dispatcher, a catalog of endpoints, and a few high-value read wrappers. Each tool earns its place without redundancy or bloat.

Completeness5/5

The combination of generic talk_get for reads, talk_invoke for writes, and talk_list_endpoints for discoverability covers the full API surface. Convenience tools for calls and devices cover the most common workflows, so there are no obvious dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues