Offprompt
OfficialServer 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 |
|---|---|
| collect_secretA | Get the values a task needs — API keys, tokens, connection strings, settings — written where the project reads them, typed by the human or generated by offprompt. Call this instead of asking the user to paste a secret into the conversation. Each entry in
Give an entry a
When every key is generated, nothing opens: offprompt writes them and returns. Otherwise it opens a page in the user's browser and this call waits there, for up to five minutes, while the human types. It returns once the values have been written or the request has expired, so there is nothing to poll and nothing to do in the meantime. In a host that ends a tool call sooner, such as Cline, it returns "awaiting" before then: call await_secret, and again while it says awaiting, with no other work in between. In a cloud sandbox or a remote VM, a browser opened there is one the user cannot see. Set You never receive a value. You get back the key names and the file they landed in, and you reference them by name from then on, for example process.env.RESEND_API_KEY. Never open, cat, grep or print that file afterwards: reading it puts the values into the transcript, which is the one thing this tool exists to prevent. The result lists every key the file holds, so there is nothing left to check. A written result opens with When the result carries a State the intent once: |
| await_secretA | Wait for a collect_secret request that came back still "awaiting" — which happens when offprompt runs in a cloud sandbox, had no browser to open and handed you the page URL to pass on, or runs in a host that ends a tool call before the human is done. Long-polls for up to 60 seconds, 50 in Cline, and returns "written", "awaiting" or "expired". Call it again while the status is "awaiting", with no other work in between. When you were given a link to pass on, an "awaiting" result carries it again: keep it in whatever you write to the user, or ask them, until the values are written. |
| cancel_secretA | Close a collect_secret request that is no longer needed. Anything already typed on the page is discarded. |
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
The tools map to distinct lifecycle stages: collect initiates a secret request, await_secret long-polls an existing request, and cancel_secret closes one. There is minor overlap because collect_secret can itself block until values are written, but the descriptions clearly delimit when to use await_secret instead.
All three tools follow the same verb_secret pattern: collect_secret, await_secret, cancel_secret. The convention is predictable and immediately readable.
Three tools are well-scoped for initiating, waiting on, and cancelling a secret-collection request. Each tool earns its place in the narrow workflow, with no redundant or filler operations.
The core lifecycle is covered: request values, wait for completion, and cancel. Minor gaps remain, such as explicitly listing existing secrets or rotating/removing a stored value, but the primary agent workflow is complete.