AI agents · Cursor
Zyntra MCP for Cursor
Add the server to Cursor's mcp.json and the agent can read your test inboxes while it works on the app that sends to them: check the email a sign-up just sent, take the link from it, clean up. It can read and delete test mail, never send it.
{
"mcpServers": {
"zyntra": {
"url": "https://mcp.zyntra.app/mcp",
"headers": { "X-API-Key": "${env:ZYNTRA_API_KEY}" }
}
}
}~/.cursor/mcp.json makes the server available in every project; .cursor/mcp.json in the repo, only in that one. Cursor fills in ${env:ZYNTRA_API_KEY} from your environment, so the key never sits in the file.
What happens to the email
- Your app sends it through its usual email provider, to an address on zyntramail.com.
- A real mail server receives it and stores it for your team, with its links pulled out of the HTML and text and its attachments kept.
- Your test reads it with one API request. Mail to an address you did not create in the dashboard is deleted after 1 day.
Check that it works
Open Cursor's MCP settings: the zyntra server should show five tools. Then ask the agent for the last email of an address you have just sent to.
Prompts to start with
- "Get the last email for [email protected] and give me the confirmation link."
- "Check whether [email protected] got a password-reset email, and show its subject."
- "List the emails in [email protected] and delete them all."
Limits to know about
get_last_emailwaits up to 30 seconds for the first email to an address; give the agent a fresh address per task so it never reads an older email.- Each tool call is one API request on your plan.
- Mail to addresses you did not create in the dashboard is kept 1 day.
Questions
- Where does the API key go?
- In an environment variable, set in your shell profile or system environment. Cursor reads it into the header through
${env:ZYNTRA_API_KEY}. - Can Cursor also drive the browser for a sign-up?
- Yes, with a browser MCP server such as Playwright MCP added next to Zyntra. See agentic testing.