list_accountsLABSCO SUMMARY
The token is the unit of access, not the vault.
A PAT carries scoped groups and an expiry, so an agent gets codes for the accounts you allowed and no others, and the seeds never leave Authn8. An ambiguous lookup returning its candidates is the other good decision here — a wrong match would otherwise fail silently as a rejected code.
What it is
A server that returns TOTP codes from an Authn8 account, authenticated by a Personal Access Token. Every tool declares an output schema and returns structuredContent beside the text, so a client gets typed results without parsing JSON back out of prose.
What you get
- Every 2FA account the token can reach, each with its id, name and issuer domain
- A current TOTP code for one account, found by id or by a case-insensitive partial name match
- An ambiguous name answered with the candidates rather than a guess — the matches come back so the next call can name an id
- The token itself described: its name, the business, the groups it is scoped to, when it expires, and how many accounts it reaches
Requirements
An Authn8 account and a Personal Access Token created in its dashboard, passed as AUTHN8_API_KEY — a pat_ token. Runs over stdio from npm as @authn8/mcp-server, or from the ghcr.io container image. AUTHN8_API_URL points it at a different API endpoint.
Setup effort
One command plus a key — npx @authn8/mcp-server, then supply credentials
USE CASES
01
Getting past a login prompt mid-task
Name the service in ordinary words and take the current code; if several accounts match, pick from the list it returns and call again by id.
02
Seeing what this agent can actually reach
List the accounts the token covers, with the issuer domain beside each name.
03
Checking a credential before you rely on it
Read the token's scoped groups, account count and expiry date, so a run does not fail halfway on an expired PAT.
3 tools
Listed in project docs. Your client may show a different list.
get_otpwhoamiBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- npx on PATH
- AUTHN8_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @authn8/mcp-serverMCP Clients
Claude Desktop, Claude Code, Cursor
JSON
{
"mcpServers": {
"authn8": {
"command": "npx",
"args": [
"-y",
"@authn8/mcp-server"
],
"env": {
"AUTHN8_API_KEY": "<YOUR_AUTHN8_API_KEY>"
}
}
}
}Docker
DOCKER · TERMINAL
docker run -e AUTHN8_API_KEY=<YOUR_AUTHN8_API_KEY> ghcr.io/authn8/mcp-server
