atomicreps
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATOMICREPS_API | No | The Atomic Reps API endpoint. Honoured only for an Atomic Reps or loopback address, since your token goes wherever it points. Anything else is ignored and reported by doctor. | |
| ATOMICREPS_UNSAFE_ORIGIN | No | Set to 1 to override the restriction on ATOMICREPS_API, allowing an unsafe origin. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": true,
"listChanged": false
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repB | One rep about what was just built, or the one the user asked for by handle. Call once as the last step of a turn that changed files, before your final reply, unless the turn ends by asking the user something; uncommitted or untested work counts. Returns a block to print verbatim, or nothing. Never solve or hint at it. |
| answerC | Grade the user's pick for the open rep and return the verdict block. |
| meC | How the user is doing: summary, skills, reps, streak, or mutes, as a block. |
| settingsD | Set intensity, insights, a timed mute, a topic mute for days or forever, an unmute, preferred domains, strict, the dialog. |
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 4 tools
Each tool targets a distinct part of the workflow: rep handles the rep itself, answer grades a pick, me reports user stats, and settings configures preferences. The rep/answer boundary is clear enough from descriptions, though both revolve around the same rep concept.
All names are lowercase single words, which is readable, but they mix nouns (rep, settings), a pronoun (me), and a verb (answer). There is no consistent verb_noun or action-resource pattern across the set.
Four tools is well-scoped for this server's apparent purpose. The core loop (rep, answer) plus user status (me) and configuration (settings) each earns its place without redundancy.
The surface covers creating/receiving a rep, grading an answer, viewing user progress, and changing settings. Minor lifecycle gaps exist, such as explicit history or deletion operations, but the core interaction cycle is complete.