Authenticator App MCP Server

What is Authenticator App MCP Server?

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 across different platforms and websites.

How to use Authenticator App MCP Server?

Add the server configuration to your MCP client’s config file using npx with the authenticator-mcp command and your Authenticator App access token. For example, on macOS/Linux: "command": "npx", "args": ["-y", "authenticator-mcp", "--access-token=YOUR-KEY"]. You can also set the AUTHENTICATOR_ACCESS_TOKEN environment variable.

Key features of Authenticator App MCP Server

• Enables AI agents to fetch 2FA codes and passwords.
• Designed specifically for the Authenticator App desktop version.
• Secure access token‑based authentication.
• Bridges AI assistants with secure credential storage.
• Supports automated login workflows across platforms.

Use cases of Authenticator App MCP Server

• AI agent retrieves a 2FA code for a specific website and account.
• AI assistant automates login by fetching stored credentials.
• Streamline multi‑factor authentication in AI‑driven workflows.

FAQ from Authenticator App MCP Server

What dependencies are required to use this server?

You need the desktop version of Authenticator App · 2FA (available for Windows, macOS, and Linux) and a valid access token generated from that app.

How do I create an access token?

Launch the Authenticator App desktop version, go to Settings → MCP Server, enable the toggle, and generate an access token. The token is shown only once, so copy it immediately.

What runtime environment is needed?

The server runs via npx (Node.js), so Node.js must be installed on your system.

Where are the 2FA codes and passwords stored?

They reside locally within the Authenticator App desktop application. The MCP server accesses them only with the provided access token.

Does the server support alternative transports or authentication methods?

The README only documents stdio‑based transport (via npx) and access‑token authentication. No other transports or auth methods are mentioned.