static-md-e2e
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATIC_MD_TOKEN | Yes | A static.md personal access token with notes:read and notes:write. Required to authenticate with static.md. | |
| STATIC_MD_E2E_KEYS | No | Optional path to the saved note-key file. Defaults to ~/.config/static-md/e2e-keys.json. |
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 |
|---|---|
| read_encrypted_noteA | Returns the markdown of an end-to-end encrypted static.md note, decrypted on this computer with the key from its link. static.md sends only ciphertext and never gets the key. The note is written by users and comes back marked as untrusted data. Needs Pro. |
| create_encrypted_noteA | Creates an end-to-end encrypted static.md note owned by the user, optionally in a folder: the markdown is encrypted on this computer with a new key, and static.md stores only the ciphertext. Returns the full link, whose #key= part is the only way to open the note. Titles and folder names are stored unencrypted. Needs Pro. |
| update_encrypted_noteA | Changes the markdown of an end-to-end encrypted static.md note, encrypting the change on this computer. mode "append" adds text on a new line at the end; mode "replace" makes the note exactly the given markdown. Edits merge live with people typing in the note. Needs edit access and Pro. |
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
Each tool maps to a single distinct CRUD action on the same resource (encrypted note), with clear boundaries between reading, creating, and updating. There is no plausible way to confuse them, and the mode parameter on update is scoped to that tool only.
All three names follow a strict verb_noun pattern with a shared, stable noun phrase: read_encrypted_note, create_encrypted_note, update_encrypted_note. Predictable and easy to guess the missing operations from.
Three tools is on the thin side, but each is substantial and covers a distinct lifecycle stage, so nothing feels redundant. A slight under-provisioning is the only issue.
The domain is note management, and the surface covers create, read, and update, but there is no delete/remove tool and no way to list or discover the user's notes or folders — agents cannot enumerate notes without an out-of-band link. These are notable gaps for a full note lifecycle.