Skip to content

Engineering

APIs, SDKs, the MCP server, and architecture: how to wire up OTP verification and run it at scale.

One spec document fanning out into four language SDK cards via thin green lines

How We Generate Our SDKs from One OpenAPI Spec

Engineering Published by otp.com Team · sdks · developer-experience

Why the otp.com client libraries for Node, Python, Go, and PHP are generated from one OpenAPI spec instead of written by hand, and how that stops drift.

Three thin green paths from REST, SDK, and MCP nodes converging on one OTP card

REST, SDK, or MCP: Choosing Your OTP Integration

Engineering Published by otp.com Team · sdks · mcp · developer-experience

Three ways to call the same OTP API: the raw REST endpoints, a generated SDK, or the MCP server for AI agents, and when each one is the right fit.

An AI agent node connected to an OTP verification card through an MCP link

Add OTP Verification to an AI Agent with MCP

Engineering Published by otp.com Team · mcp · ai

Point any MCP client at the otp.com server and your AI agent can send, verify, resend, and check one-time passwords using only your API key.