Authenticator App MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTHENTICATOR_ACCESS_TOKEN | Yes | Your Authenticator App access token generated from the desktop app |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_2fa_codeC | Retrieve the current 2FA code for a username when logging into a website. |
| get_passwordC | Retrieve the password for a username when logging into a website. |
| get_account_listC | Retrieve the accounts can be used when logging into a website. |
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 has a clearly distinct purpose: get_2fa_code retrieves time-based codes, get_account_list lists available accounts, and get_password retrieves passwords. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with 'get_' prefix (get_2fa_code, get_account_list, get_password). The naming is uniform and predictable, using snake_case throughout without any deviations.
With only 3 tools, the server feels thin for an authenticator app domain that might benefit from operations like adding/removing accounts or updating credentials. While the tools cover core retrieval needs, the count is borderline minimal for comprehensive functionality.
The toolset is severely incomplete for an authenticator app, lacking any write operations such as adding accounts, updating passwords, or managing 2FA settings. Agents can only retrieve data, leading to dead ends for common workflows like account setup or credential changes.