Zona MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZONA_SOURCE_TOKEN | No | Source token for Zona. If not provided, the server reads the token from ~/.zona/token (or %USERPROFILE%\.zona\token on Windows). |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zona_statusA | Check that the local Zona source-token file exists. Never returns the token. |
| zona_notifyA | Send an inbox notification to the owner's Zona app. Title 1-120 chars, body 1-2000. Optional category, severity (low|medium|high|critical), up to five PNG/JPEG/WebP attachment paths, and an idempotency key. Do not put secrets in title, body, or data. |
| zona_pingB | Send a short test notification to confirm the local token and /notify path work. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
zona_status clearly checks token-file existence, while zona_notify sends a full notification and zona_ping sends a test notification. The only minor overlap is between notify and ping, but the test nature of ping is clear enough to avoid real ambiguity.
All tools use a consistent 'zona_' prefix followed by a short, recognizable action word: status, notify, ping. The naming pattern is uniform and predictable.
Three tools is small but appropriate for a narrow notification-focused server. It covers status validation, actual sending, and testing without unnecessary bloat.
The domain is simple: verify the token, send a notification, and test connectivity. These three operations cover the essential workflow, though a tool to validate token permissions or list recent notifications could be a minor addition.