Achromat MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACHROMAT_BASE_URL | No | The service origin. Must be `https` (plain `http` only for `localhost`). | https://mom.achromat.ai |
| ACHROMAT_AGENT_KEY_FILE | No | Where the agent's Ed25519 private key is, or will be created. By default the key is at `~/.achromat/achromat_agent_key.pem`. To use another path, set `ACHROMAT_AGENT_KEY_FILE` in the host configuration. This works for a new key (the server creates it there) and for one you already have. On Windows use the full path with escaped backslashes, for example `"C:\\Users\\you\\keys\\achromat_agent_key.pem"`. A leading `~` is expanded by the server. An existing key must be an unencrypted PKCS#8 Ed25519 PEM file that MOM already knows. | ~/.achromat/achromat_agent_key.pem |
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 |
|---|---|
| achromat_register_identityA | Achromat needs a private key on this machine before it can answer anything, and none exists yet. This tool creates one: it generates an Ed25519 key pair, completes a short proof of work (about a second), registers the public key with Achromat MOM, and saves the private key to a file that only this user can read. ASK THE USER FIRST and wait for a yes, because it writes a private key file on their machine and creates an identity on the service. Explain that the key never leaves the machine, that only the public half is sent, and that the file cannot be recovered if lost. Then call this tool with user_confirmed set to true. Afterwards achromat_recall and achromat_calibrate become available. |
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 1 tool
With only one tool exposed there is no overlap risk, so selection is trivially unambiguous. However, the description references achromat_recall and achromat_calibrate as if they were sibling tools, which an agent may search for and not find, adding mild confusion.
The single name achromat_register_identity follows a clear namespace_verb_noun snake_case convention that would obviously extend to the other referenced tools (achromat_recall, achromat_calibrate). No inconsistent styles are present.
One tool is far too thin for a service whose own description implies at least three operations (register, recall, calibrate). Registration alone leaves the server nearly unusable, even if the remaining tools are dynamically unlocked later.
The surface covers only identity bootstrap; there is no way to recall information or calibrate, which are presented as the core capabilities. An agent can register an identity but has no follow-up operations, creating an immediate dead end.