Can I use MailVakt across projects?

Yes. Put the same server entry in your user-level ~/.cursor/mcp.json instead of the project file. Merge it with your existing configuration.

Will MailVakt change my DNS or send email as me?

No. Domain checks read public DNS and return findings and suggested fixes. You make any DNS edits yourself. For an inbox test, you send a message to a temporary test address; MailVakt does not send it for you.

Does fixing these records guarantee inbox placement?

No. Authentication is one part of deliverability. Sender reputation, message content and recipient behavior also matter. MailVakt helps you find and address configuration problems.

← All integrations

MailVakt + Cursor

Debug email delivery without leaving Cursor

When a signup email or password reset goes missing, give Cursor Agent your domain’s actual DNS findings alongside your application context.

Connect Cursor Try a domain check

Free public checks · No DNS access needed · You stay in control of changes

Inspect your domain

Check live email DNS records, including SPF, DKIM and DMARC, without handing over your DNS login.

Understand the findings

Ask Cursor to explain failures and help prioritize the problems that could affect delivery.

Get a fix you can review

Get proposed record names and values. MailVakt does not edit DNS; you apply approved changes at your provider.

Get connected

Set up MailVakt in Cursor

Use a current version of Cursor with Agent and MCP enabled. Your organization may restrict which servers you can add.

Open or create .cursor/mcp.json in your project. Merge the mailvakt entry below into its mcpServers object, preserving any existing servers.
Save the file and check that MailVakt is enabled in Cursor’s MCP settings. Complete sign-in if you need account-linked tools.
Open Agent, ask it to use MailVakt, and approve the relevant tool calls. Start with the sending domain used by your application.

.cursor/mcp.json

{
  "mcpServers": {
    "mailvakt": {
      "url": "https://mcp.mailvakt.com/mcp"
    }
  }
}

Public checks and inbox tests need no MailVakt account. Sign in when prompted to manage domains or read DMARC summaries. Your assistant may ask you to connect an account during setup.

Setup guidance checked October 9, 2026. Official Cursor setup documentation.

Start with a question

Replace example.com with your sending domain, then paste a prompt into Cursor.

Use MailVakt to check example.com, the sending domain for my app’s password resets. Summarize the email DNS problems.

Use MailVakt to inspect example.com for SPF and DMARC issues before I launch transactional email.

Use MailVakt to propose DNS records for the failures on example.com. Keep those changes separate from application code changes.

Questions

Can I use MailVakt across projects?: Yes. Put the same server entry in your user-level ~/.cursor/mcp.json instead of the project file. Merge it with your existing configuration.
Will MailVakt change my DNS or send email as me?: No. Domain checks read public DNS and return findings and suggested fixes. You make any DNS edits yourself. For an inbox test, you send a message to a temporary test address; MailVakt does not send it for you.
Does fixing these records guarantee inbox placement?: No. Authentication is one part of deliverability. Sender reputation, message content and recipient behavior also matter. MailVakt helps you find and address configuration problems.

Use MailVakt with another tool