serve
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| account_statusA | Account-level state: plan, entitlement, and how much of the storage, transfer and publish allowance is used. Use this to check what the account may do or whether it is near a limit. For the links themselves (labels, URLs, protection state), use links instead. Owned links are unlimited by count. |
| create_viewer_grantA | Create a single-use owner-browser bypass grant (Pro plan required) and return a bypass URL for the link. Use it to open a protected link in the browser without sharing the link's viewer credential; it is not a general viewer-sharing credential. The grant is valid for two minutes after creation and can be used once. |
| doctorA | Run self-diagnostics when a link is unreachable or a call fails: config and identity fingerprint presence, account API health, relay health, and outbound UDP 443 (QUIC) reachability, each reported as a check result. The probes are best-effort and need no login; a UDP probe that sends but gets no reply is inconclusive, not proof of failure. For plan and quota, use account_status; for the account's link inventory, use links; for a single tunnel's state, use tunnel_status. |
| linksA | Inventory of every owned link (label) for the account, one record each: kind, URL, live/stale markers, protection status, last bound/viewer activity, and quarantine window. Use this to see what is currently served or published, or to find a label to act on. Live-tunnel capacity (live/max) and storage, transfer and publish-rate usage come along as context. For plan, entitlement and quota headroom, use account_status instead. Owned links are unlimited by count. |
| list_tunnelsA | List all active tunnels in this manager with their ports, labels, public URLs, uptime, state, and last error. To inspect a single tunnel, use tunnel_status with its port or label. |
| protect_linkA | Enable capability token and readable secret protection on an owned link (Pro plan required). Returns the share URL (with #cap=...) and the human-readable secret code. If label is omitted, the first owned link returned by links is protected. If ttl is omitted, protection lasts 24 hours. Calling this on an already-protected link replaces the existing credentials, so previous share URLs stop working. To rotate credentials instead, use renew_link; to change only the duration, use update_ttl. |
| release_linkA | Release (free) an owned link by label. Fails with remote_link while the label still has a published artifact; unpublish it with stop_remote first. Returns confirmation and the account's usage. |
| renew_linkA | Rotate the capability token and secret code for a link (Pro plan required): fresh credentials are minted and the countdown restarts, and the previous credentials stop working immediately. If ttl is omitted, protection defaults to 24 hours. For a duration-only change without rotating credentials, use update_ttl instead. |
| revoke_linkA | Immediately revoke the active secret code and capability token for a link while keeping owner access intact. The link stays protected, so the old share URL and secret stop working; no new credentials are minted. To open the link to everyone instead, use unprotect_link; to mint fresh credentials, use renew_link. |
| serveA | Publish a local resource to a public HTTPS URL. Pass path to serve a file or directory (auto-hosted, no separate server needed), or port to expose an already-running dev server. Set residency to "remote" to publish the path to serve's storage so the URL works with the machine off. Do NOT start your own static file server; pass exactly one of path or port. Returns the public url, label, and residency, with label_kind and status for live links (or version, size_bytes, and kind for remote publishes); served_path and protection fields appear when set; usage comes along as context. |
| serve_fileA | Serve a local file or directory and get a public shareable URL. Pass the file or directory path to path to have it auto-hosted and tunneled. Use this when the user asks to share/serve a file, markdown document, image, or artifact. Set residency to "remote" to publish to serve's storage so the URL works with the machine off. Do not start your own static server. To expose an already-running dev server by port instead, use the serve tool. |
| stop_all_tunnelsA | Stop every active tunnel, revoking all public URLs. To stop a single tunnel, use stop_tunnel instead. |
| stop_remoteA | Unpublish a remote link, deleting its stored artifact bytes immediately and returning the link to local residency. Use links to see published (remote) links. To stop a live tunnel, use stop_tunnel instead; this tool only removes published bytes. |
| stop_tunnelA | Stop (tear down) the tunnel for a local port or link label, revoking its public URL. Idempotent. To change a live tunnel's port or label, stop it here and then call serve again with the new settings; there is no in-place reconfiguration. |
| tunnel_statusA | Return the status of a single tunnel identified by its local port or its link label, including public URL, uptime, state, and last error. To see every active tunnel at once, use list_tunnels instead. |
| unprotect_linkA | Clear protection on an owned link, returning it to public access. Use this to open up a protected link so anyone with the URL can view it. To keep the link protected but invalidate its current credentials, use revoke_link; to free the label entirely (and fail while a remote artifact is still published), use release_link. Requires ownership of the link. |
| update_ttlA | Change the protection duration (TTL) of an already-protected link (Pro plan required) without rotating its credentials. The link must currently be protected with an unexpired credential; expired protection must be renewed first with renew_link. The expiration is recalculated from the new duration, not extended from the previous expiry. |
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 17 tools
The toolset is mostly clear: serve, protect_link, renew_link, revoke_link, unprotect_link, stop_tunnel, and stop_remote each target distinct actions. However, serve and serve_file overlap heavily—both publish local files/directories to public URLs—creating real selection ambiguity without careful reading.
Most tools follow a clear verb_noun pattern like protect_link, renew_link, stop_tunnel, and update_ttl. Deviations such as bare serve, plural links, and noun doctor break the pattern slightly but are still readable and predictable overall.
17 tools cover serving, tunneling, remote publishing, protection, diagnostics, and account status, which is slightly heavy but mostly justified by the lifecycle operations. The redundant serve_file adds padding, but the overall count is within a reasonable scope.
The surface covers link lifecycle, protection rotation/revocation unprotection, tunnel management, remote publishing, account status, and diagnostics with no obvious dead ends. Cross-references between tools fill gaps, and core workflows like serve, protect, renew, revoke, stop, and release are all present.