Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
--profileNoWhich identity directory this process uses. Letters, digits, `.`, `_` and `-`, up to 64, and it may not start with a dot.claude-code
DO_NOT_TRACKNo`1` turns usage reporting off. Read only to turn it off.
ZAS_API_BASENoThe API.https://zas.red/api
ZAS_WEB_BASENoThe web app the pairing URL points at.https://zas.red
ZAS_OPRF_BASENoThe blind key-derivation service.https://zas.red/oprf
ZAS_AGENT_HOMENoWhere the profile directories live.~/.zas/agent
ZAS_TOKEN_BASENoThe challenge and token routes.https://zas.red/anon-token
ZAS_AGENT_TELEMETRYNo`0` turns usage reporting off for this process, `1` on. It outranks the stored choice.
ZAS_FIREBASE_API_KEYNoThe key used to exchange a custom token for a session. Defaults to the public web key.
ZAS_FIREBASE_PROJECTNoThe project whose Firestore the read path queries.zas-me

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
zas_statusA

Say whether this agent is paired with a Zas account, and list the owner's channels it may send to or read from. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_pairA

Pair this agent with a Zas account. The first call returns a URL for the owner to open; a later call says whether they approved. If the page shows a code, call again with code. In a profile that is already paired, approval replaces the old agent. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_send_fileA

Send a file from this machine into one of the owner's Zas channels. Returns the item id, or a job id when the upload takes longer than a minute. A channel in Directo mode refuses this tool: use zas_send_direct there. Sends any file this process can read; confirm with the owner before sending secrets, keys or credentials. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_send_directA

Send a file from this machine through Directo: a live, device-to-device transfer into one of the owner's channels that is in Directo mode. Nothing is stored. The owner has to press Receive on another device within ten minutes; the call waits a minute and then returns a job id to check with zas_jobs. Returns the transfer result, or a job id. Sends any file this process can read; confirm with the owner before sending secrets, keys or credentials. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_send_direct_fallbackA

After a zas_send_direct job failed in flight, deliver the same file through reliable delivery instead. Zas encrypts the file on this machine and stores only that encrypted copy in Cloudflare R2 for up to 24 hours; it uses none of the owner's space, and the device that claimed the offer can download it later. This stops being Directo: the encrypted bytes pass through storage. Ask the owner before you use it; it is their choice. Pass the failed job's id. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_receive_directA

Receive a file the owner sends through Directo, straight onto this machine. Call it when the owner says they are sending you something: it waits for the offer, takes it, and writes the file to disk. Nothing is stored anywhere. Only for a channel in Directo mode, and only with a grant that includes reading. The call waits a minute and then returns a job id to check with zas_jobs; the wait for an offer alone can take ten minutes. Returns the path written; it never overwrites an existing file. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_receive_direct_fallbackA

After a zas_receive_direct job failed in flight, download the encrypted copy the sender chose to store instead. It works only if the person who was sending picked reliable delivery for that transfer. The file is decrypted on this machine and written to the same destination. Pass the failed job’s id. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_send_noteB

Send a note — plain text, or a code snippet with its language — into one of the owner's Zas channels. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_list_itemsB

List the most recent items in one of the owner's Zas channels. Needs a grant that includes reading. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_get_itemA

Fetch one item from a Zas channel. A note comes back as text; a file is written to disk. Returns the path written; it can differ from dest when a file with that name already exists. Writes a new file under dest (or the system temp directory); it never overwrites an existing file. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_edit_itemA

Change an item this agent sent, keeping its id: the title of a file or a note, or a note's text, language and secret cover. Refuses items sent by anyone else. A file's bytes change with zas_replace_file. Needs a grant that includes reading and sending. Pass only the fields to change; an empty title clears it. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_replace_fileA

Replace the bytes of a file this agent sent with a file from this machine, keeping the item id, its place in the channel and its pin. Refuses items sent by anyone else, notes, and an item with a public share. Returns the item id, or a job id when the upload takes longer than a minute. Sends any file this process can read; confirm with the owner before sending secrets, keys or credentials. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

zas_jobsA

List the sends and Directo transfers this server started, newest first, with the phase each one reached and how it ended — including any job_id a send returned; a finished job keeps its result here. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 13 tools

Disambiguation4/5

Most tools target distinct actions: pairing/status, sending notes/files, Directo transfers, receiving, job tracking, and item editing are separable. Some boundaries are subtle—especially zas_send_file vs zas_send_direct and the two fallback tools vs their primary operations—but descriptions clarify channel mode and failure context.

Naming Consistency4/5

All tools use a consistent zas_ prefix and snake_case naming. Most follow a verb_noun pattern, with minor deviations such as zas_status and zas_jobs being noun-like, but the convention remains readable and predictable.

Tool Count5/5

Thirteen tools is well within the appropriate range for this domain, covering pairing, sending, receiving, job tracking, and item lifecycle. The fallback and direct-transfer variants each earn their place by handling distinct operational modes.

Completeness4/5

The surface covers core lifecycle operations: pair/status, send note/file, direct send/receive, fallbacks, list/get/edit/replace items, and jobs. A notable gap is item deletion or unpairing, though agents can work around these for most workflows.

Maintenance

ActivityActive
ResponsivenessUnresponsive