The Authenticator App MCP Server enables AI agents to securely retrieve authentication credentials for automated login processes. It provides three key functions:
Retrieve 2FA codes for specific website/username combinations
Fetch passwords for specific website/username combinations
Obtain lists of accounts available for login to specific websites
Supports the Debian version of Authenticator App · 2FA through .deb package installation, enabling AI agents to retrieve secure authentication credentials.
Supports the desktop version of Authenticator App · 2FA on Linux platforms, enabling AI agents to access authentication credentials securely.
Supports the desktop version of Authenticator App · 2FA on macOS, allowing AI agents to securely retrieve 2FA codes and passwords for automated login processes.
Provides compatibility with the Ubuntu/Debian version of Authenticator App · 2FA through .deb package installation, allowing secure access to authentication credentials.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Authenticator App MCP Server get my 2FA code for GitHub"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A secure MCP (Model Context Protocol) server that enables AI agents to interact with the Authenticator App. It provides seamless access to 2FA codes and passwords, allowing AI agents to assist with automated login processes while maintaining security. This tool bridges the gap between AI assistants and secure authentication, making it easier to manage your credentials across different platforms and websites.
Open your AI agent's integrated chat interface (such as Cursor's agent mode).
Ask AI agent to retrieve your 2FA code or password for your desired website and account.
AI agent will securely fetch these credentials, then can utilize them to automate your login process.
This MCP server is specifically designed for use with Authenticator App · 2FA.
Related MCP server: ssh-mcp-server
Many AI clients use a configuration file to manage MCP servers.
The authenticator-mcp tool can be configured by adding the following to your configuration file.
NOTE: You will need to create a Authenticator App access token to use this server. Instructions on how to create a Authenticator App access token can be found here.
{
"mcpServers": {
"Authenticator App MCP": {
"command": "npx",
"args": ["-y", "authenticator-mcp", "--access-token=YOUR-KEY"]
}
}
}{
"mcpServers": {
"Authenticator App MCP": {
"command": "cmd",
"args": ["/c", "npx", "-y", "authenticator-mcp", "--access-token=YOUR-KEY"]
}
}
}Or you can set AUTHENTICATOR_ACCESS_TOKEN in the env field.
Launch the desktop version of Authenticator App · 2FA.
Navigate to Settings and locate the MCP Server section.
Enable the MCP Server by toggling it ON, then proceed to generate your access token.
Please note that the access token will only be displayed once. Be sure to copy it immediately and add it to your MCP client configuration.
Retrieve the current 2FA code for a username when logging into a website.
Inputs: username (required), website (required).
Retrieve the accounts can be used when logging into a website.
Inputs: website (required).
Retrieve the password for a username when logging into a website.
Inputs: username (required), website (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Shared 2FA for teams: let AI agents get TOTP codes for the accounts your Authn8 token can see.
Logs your AI agent into websites, catches verification codes, and asks you before anything risky.
Password vault for AI agents with scoped, user-approved access
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
