@mgcrea/mcp-totp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOTP_DEBUG | No | Set to any value to enable verbose stderr logging. | |
| TOTP_ALLOW_WRITES | No | Set to '1' to register the seed-importing and seed-removing tools. Off by default. | 0 |
| TOTP_SECRET_<LABEL> | No | A seed supplied by environment for Docker/CI where there is no keychain. Either an otpauth:// URI or a bare base32 key. Replace <LABEL> with a label (lower-case letters, digits and underscores, starting alphanumeric). | |
| TOTP_KEYCHAIN_SERVICE | No | Keychain service the seeds are filed under. Defaults to com.mgcrea.mcp-totp. | com.mgcrea.mcp-totp |
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 |
|---|---|
| totp_auth_statusA | Report what this server can and cannot do: whether a seed store is reachable, which labels are registered and where each one comes from, and whether writes are enabled. Call this first when a tool you expected is missing — an absent tool means missing configuration rather than a bug. Note what this server is NOT: it cannot read codes out of Passwords.app. No such interface exists — Passwords.app has no scripting dictionary and no App Intents, and its keychain items sit behind an Apple-private access group. This server holds its own copy of the seed and mints codes locally; totp_import_uri can hand the same seed to Passwords.app so both stay in sync. |
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 possibility of selecting the wrong tool. The tool's purpose as a status/diagnostic endpoint is clearly distinct from any other functionality.
The single tool name uses consistent snake_case and clearly indicates its role as a status report. With no other tools, there is no naming pattern to conflict.
A single status tool is far below the expected scope for a TOTP server, which should include operations for key management and code generation. The description even references a totp_import_uri tool that is not exposed, making the set feel incomplete.
The tool only reports capabilities and configuration state; there are no tools to actually create, import, or use TOTP secrets. This is a severe gap for a server named mcp-totp.