Replyz / Cursor

Give Cursor's agent its own email inbox.

Add the Replyz MCP server and Cursor's agent can create email addresses, wait for messages and read verification codes while it builds and tests your app. Your personal email stays out of it.

Get early access The MCP server

How do you add Replyz to Cursor?

Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it everywhere:

{
  "mcpServers": {
    "replyz": {
      "url": "https://mcp.replyz.io/mcp",
      "headers": {
        "Authorization": "Bearer ${env:REPLYZ_API_KEY}"
      }
    }
  }
}

Set REPLYZ_API_KEY in your shell profile. Cursor reads ${env:…} values from the environment, so the key never sits in the file.

What can Cursor's agent do with it?

Test sign-up flows

Check reset links

Trigger a password reset, wait for the email and open the link to see that it works.

Read email templates

Fetch what your app actually sent and compare it with what you expected.

Sign up for dev services

Create accounts for the APIs a project needs without your personal address.

What can you ask it?

"Create a Replyz inbox and register a test user on localhost:3000."
"Wait for the verification email and check the link returns 200."
"Trigger a password reset and show me the email body."

Frequently asked questions

How do I add Replyz to Cursor?

Add a replyz entry to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project, with the Replyz MCP URL and an Authorization header that reads your key from the environment.

Where does the API key go?

In an environment variable such as REPLYZ_API_KEY. Cursor resolves ${env:REPLYZ_API_KEY} in the headers, so the key isn't written into mcp.json.

What is it useful for in Cursor?

Testing sign-up and password-reset flows end to end: the agent registers a test user with its own address, waits for the email and checks the link works.

Is my personal email involved?

No. The agent only sees mail sent to the Replyz addresses it creates.