Introducing Mailisk MCP

Mailisk now supports the Model Context Protocol (MCP), letting coding agents and automation tools create unique test email addresses, wait for matching inbound emails, and extract code or URL candidates during development and QA.

Why MCP for email testing?

Email testing often sits awkwardly between the app, the test runner, and the developer. You need an address that will not collide with another test run, you need to trigger the app, and you need to wait for the email without accidentally reading an older message.

With Mailisk MCP, an agent can handle that coordination from inside the workflow it is already helping with. It can generate a unique address, tell you where to use it, then wait for the exact matching email using the timestamp returned when the address was created.

This is useful for both local development and CI debugging. Instead of switching between the dashboard, API docs, and test code, you can keep the email loop available as tools the agent can call.

Current use cases

Sign-up and email verification

For sign-up flows, the agent can call create_email_address, use the generated address in your registration form, then call wait_for_email to read the verification email.

That makes it easier to validate:

• The sign-up form accepts new addresses.
• The verification email is delivered.
• The email is sent to the expected recipient.
• The body contains the right verification link or code.

An example prompt:

Create a Mailisk email address, register a new test user with it, then wait for the verification email and extract the verification link.

Password reset flows

Password resets are a good fit because each run should use a fresh recipient and should ignore old reset emails.

The agent can generate an address, create or target a test user, request a password reset, then wait for the reset email. Since wait_for_email uses the from_timestamp returned by create_email_address, it can avoid matching reset emails from earlier runs.

This helps catch regressions in:

• Reset email delivery.
• Reset token generation.
• Email copy and link format.
• End-to-end reset completion.

Magic links and one-time codes

Magic link and OTP flows need the same pattern: trigger an email, wait for it, parse the value, then continue.

With the current MCP tools, an agent can receive the email and use the returned extracted.codes or extracted.urls candidates to continue testing the login flow when the right value is clear. If it needs to inspect the email copy, it can call wait_for_email with include_text: true or include_html: true, but the default response stays compact so large email templates do not fill the agent context.

Transactional email checks

For product workflows that send confirmations, receipts, exports, or notifications, the MCP flow gives agents enough access to verify that the email arrived and contains the expected content.

Examples:

• Order confirmation emails.
• Billing receipt notifications.
• Export-ready emails.
• Comment, mention, or workflow notifications.
• Security alerts.

Configuring Mailisk MCP

Create an MCP API key in the Mailisk dashboard. MCP keys are separate from regular REST API keys and start with sk_mcp_.

Replace sk_mcp_YOUR_API_KEY with the key from your dashboard.

Most MCP clients use JSON configuration:

{
  "mcpServers": {
    "mailisk": {
      "url": "https://api.mailisk.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_mcp_YOUR_API_KEY"
      }
    }
  }
}

The hosted MCP endpoint is:

https://api.mailisk.com/mcp

For more setup details see the MCP configuration docs.