MCP Server

The Trivumo MCP server lets AI agents and coding assistants generate disposable email addresses, list inbox messages, and read full message content — including extracted links, verification codes, and images.

Use it to automate email verification flows, debug signup journeys, or give an agent direct access to your team's test inboxes without writing custom API calls.

Prerequisites

Before connecting, make sure you have:

• A Trivumo account with an active team
• A Trivumo API key (available on your dashboard)
• A domain configured for your team

Authentication

All MCP requests require your Trivumo API key in the Authorization header:

Authorization: ApiKey YOUR_API_KEY

The key is scoped to your team. Every tool runs in that team's context, so messages and generated addresses belong to your configured domain.

Server URL

Trivumo exposes a streamable HTTP MCP endpoint at:

https://trivumo.com/mcp-server/mcp

Connect a Client

Cursor

Add the server to your Cursor MCP configuration (.cursor/mcp.json):

{
  "mcpServers": {
    "trivumo": {
      "url": "https://trivumo.com/mcp-server/mcp",
      "headers": {
        "Authorization": "ApiKey YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop

For clients that only support stdio transport, use mcp-remote as a bridge:

{
  "mcpServers": {
    "trivumo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://trivumo.com/mcp-server/mcp",
        "--header",
        "Authorization: ApiKey YOUR_API_KEY"
      ]
    }
  }
}

Windsurf and other MCP clients

Any client that supports streamable HTTP can connect directly using the server URL and Authorization header shown above.

Tools

generate_email

Generate a random disposable email address on your team domain.

Example response:

{
  "email": "x7k2m9qp@sandbox.trivumo.com",
  "domain": "sandbox.trivumo.com"
}

get_messages

Retrieve paginated inbox messages for your team. Results can be filtered by recipient, sender, subject, and received timestamp.

Example response:

{
  "data": [
    {
      "id": "...",
      "referenceId": "abc123",
      "subject": "Verify your account",
      "from": "noreply@example.com",
      "to": "x7k2m9qp@sandbox.trivumo.com",
      "receivedAt": "2026-06-20T12:00:00.000Z"
    }
  ],
  "page": 1,
  "totalPages": 1
}

get_message

Retrieve the full content of a single message by its referenceId, including HTML and plain-text bodies, headers, extracted links, verification codes, and images.

Example response:

{
  "success": true,
  "referenceId": "abc123",
  "subject": "Verify your account",
  "from": "noreply@example.com",
  "to": "x7k2m9qp@sandbox.trivumo.com",
  "receivedAt": "2026-06-20T12:00:00.000Z",
  "headers": [],
  "html": {
    "body": "<p>Your code is <strong>482910</strong></p>",
    "codes": ["482910"],
    "links": [{ "href": "https://example.com/verify", "text": "Verify" }],
    "images": []
  },
  "text": {
    "body": "Your code is 482910",
    "codes": ["482910"],
    "links": [],
    "images": []
  }
}

Example Workflow

A typical email verification flow with an AI agent:

1. Call generate_email to create a disposable address.
2. Use that address to sign up in the application under test.
3. Call get_messages with the to filter set to the generated address.
4. Call get_message with the returned referenceId to read the verification link or OTP.

Error Handling

Tools return errors as MCP tool results with isError: true. Common cases:

Related

• Node.js SDK — programmatic access from test suites
• API Reference — REST endpoints for the same inbox data