LabscoMCP early access ↗
andreax79MCP SERVER

OTP MCP Server

Keep OTP tokens where the assistant can reach them: add_token registers one from its secret, list_otp_tokens says what is stored, and calculate_otp_codes returns the current code for every token matching a pattern.

by andreax79 ↗Identity, Access, Secrets & EncryptionCommunity

LABSCO SUMMARY

A pattern, not a token name, is the unit of address — and that applies to deletion exactly as it applies to code generation.

get_details, calculate_otp_codes and delete_token all take pattern, so a pattern loose enough to be convenient when fetching a code reaches just as widely when the call is delete_token. The store runs locally and holds no account of its own: what it keeps is the secret handed to add_token, alongside the account, issuer, type, algorithm, digits, period and counter that describe it.

What it is

A local OTP token store, exposing token listing, detail lookup, code calculation, and adding or deleting tokens.

What you get

  • list_otp_tokens returns the tokens held, which is what establishes what can be generated before a code is asked for.
  • get_details returns the details of the tokens matching a pattern, and calculate_otp_codes returns the current code for the tokens matching one.
  • add_token registers a token from its secret, together with account, issuer, type, algorithm, digits, period and counter.
  • delete_token removes the tokens matching a pattern.

Requirements

Nothing — no account, no key.

Setup effort

One command — uvx otp-mcp-server