Introducing Mailisk MCP

Mailisk now supports the Model Context Protocol (MCP), letting coding agents and automation tools generate unique test email addresses, inspect inbound email and SMS workflows, send outbound email, and extract code or URLs during development and QA.

Why MCP for email and SMS testing?

Testing email and SMS workflows often requires coordinating several moving parts: setting up an isolated recipient, triggering the application, and waiting for the resulting message.

With Mailisk MCP, an agent can handle message-testing tasks from inside the workflow it is already helping with, including setting up a recipient, waiting for the resulting email or SMS, and sending email.

This is useful for local development, manual QA, writing tests, and CI debugging. The agent can use message-testing tools directly while it builds, verifies, or debugs a flow.

Potential use cases

Sign-up and email verification

For sign-up flows, an agent can register a user with a unique test address, wait for the verification email, and check that it contains the expected link or code.

An example prompt:

Sign up for an account then confirm that the verification email contains a verification link.

Password reset flows

For password reset flows, an agent can request a reset for a test user, wait for the email, and use the link to complete the reset.

An example prompt:

Request a password reset for a test account, then use the link in the email to set a new password.

Magic links and one-time codes

For magic-link and one-time-code flows, an agent can retrieve the login link or code from an incoming email and use it to continue the sign-in flow.

An example prompt:

Sign in to a test account using the one-time code sent by email.

SMS verification and passwordless flows

For SMS verification and passwordless flows, an agent can retrieve a code or link from an incoming text message and use it to continue the test.

An example prompt:

Sign in to a test account using the one-time code sent by SMS.

Transactional email checks

For workflows that send confirmations, receipts, exports, notifications, or security alerts, an agent can confirm that the email arrives and contains the expected information.

An example prompt:

Place a test order, then confirm that the order confirmation email shows the correct items and total.

Outbound email workflows

An agent can send email, reply to or forward a received message, and check its delivery status. Because these actions affect external systems, they should only be used when the requested workflow requires them.

An example prompt:

Reply to the latest email from a test customer, then confirm that the reply was delivered.

History inspection and debugging

An agent can search recent email history to find a message, check for duplicate sends, or investigate a failed test.

An example prompt:

Check whether more than one welcome email was sent to the test user after sign-up.

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 docs.