Zyntra - Temp e-mails MCP

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL

https://heyclau.de/entry/mcp/zyntra-mail

Source URLs

https://docs.zyntra.app/mcp, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/zyntra-mail.mdx

Brand

Zyntra

Brand domain

zyntra.app

Brand asset source

brandfetch

Safety notes

Use disposable inboxes only for test or low-risk flows and avoid receiving real user, password-reset, or secret-bearing email.

Privacy notes

Email addresses, message contents, delivery links, extracted fields, and API credentials may be sent through tool calls.

Author

dd77ss

Submitted by

dd77ss

Original submission

https://github.com/JSONbored/awesome-claude/issues/310

Import PR

https://github.com/JSONbored/awesome-claude/pull/314

Reviewed by

JSONbored

Claim status

unclaimed

Last verified

2026-04-30

• Email addresses, message contents, delivery links, extracted fields, and API credentials may be sent through tool calls.

Show that Zyntra - Temp e-mails MCP is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/zyntra-mail.svg)](https://heyclau.de/entry/mcp/zyntra-mail)

Zyntra - Temp e-mails MCP side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	Zyntra - Temp e-mails MCP MCP server for e-mail testing: create disposable inboxes, wait for delivery, and extract e-mail content or links - all from your AI agent or test automation workflow. Get a free API key on https://app.zyntra.app/ Open dossier	Agent Device MCP Server Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps. Open dossier	BrowserMCP Server Browser automation MCP server and Chrome extension that lets AI applications control a connected tab in the user's existing browser profile. Open dossier	Firefox DevTools MCP Mozilla-maintained MCP server for automating Firefox through WebDriver BiDi, with tools for page navigation, snapshots, UID-based input, screenshots, network requests, console messages, dialogs, history, viewport changes, optional JavaScript evaluation, privileged Firefox contexts, preferences, and WebExtension. Open dossier
Trust	Review first	Review first	Review first	Review first
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	Zyntra	agent-device	BrowserMCP	—
Category	mcp	mcp	mcp	mcp
Source	source-backed	source-backed	source-backed	source-backed
Author	dd77ss	Callstack	BrowserMCP	Mozilla
Added	2026-04-30	2026-06-06	2026-06-05	2026-06-06
Platforms	Claude CodeCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓Use disposable inboxes only for test or low-risk flows and avoid receiving real user, password-reset, or secret-bearing email.	✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP. Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions. Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files. Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work. Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts.	✓BrowserMCP can navigate pages, click controls, type text, submit forms, capture screenshots, inspect accessibility snapshots, read console logs, and automate the connected tab. Because it uses the user's real browser profile, logged-in sessions and account permissions may be available to the agent. Require human approval before purchases, messages, account changes, destructive actions, or actions that violate a site's terms. Use a test profile or non-production account for end-to-end testing and repetitive automation.	✓Browser pages can contain prompt-injection text in visible content, hidden HTML, ARIA labels, console output, network responses, or page metadata. The server can navigate pages, click, hover, fill forms, drag, upload files, accept dialogs, dismiss dialogs, go through history, change viewport size, close tabs, and restart Firefox. Enabling evaluate_script allows arbitrary JavaScript in page context; compromised instructions could read page data, modify the DOM, or interact with accessible browser APIs. Enabling privileged context tools with the required Firefox system-access environment variable can expose privileged Firefox APIs and may extend beyond web-content sandbox boundaries. Connect-existing mode can attach to a real browsing session with cookies, logins, active tabs, history, and saved state, so avoid it unless the profile is dedicated to automation. Accepting insecure certificates weakens TLS validation and can hide man-in-the-middle or misconfiguration signals.
Privacy notes	✓Email addresses, message contents, delivery links, extracted fields, and API credentials may be sent through tool calls.	✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials. macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts. Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing. Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set.	✓Connected tab content, screenshots, form fields, console logs, and page state may be exposed to the MCP client and model. Logged-in pages can contain personal data, customer information, credentials, tokens, internal URLs, or private documents. Although the project describes local automation, prompts and tool results still flow through the chosen AI application and model provider.	✓Page content, DOM snapshots, accessibility labels, console messages, network requests, headers, screenshots, uploaded file paths, extension names, Firefox prefs, and browser logs can be sent to the MCP client and model. A regular Firefox profile can expose cookies, saved sessions, browsing history, account data, extensions, and private tabs to browser automation. Screenshot save paths, uploaded files, downloaded artifacts, and model transcripts can reveal local project names, test data, credentials shown on pages, or customer information. Use a separate profile, minimize enabled capabilities, avoid sensitive sites, and review provider/browser data handling before automating logged-in sessions.
Prerequisites	— none listed	Node.js 22 or newer and `agent-device` installed globally or project-locally. Xcode tooling for iOS, tvOS, or macOS targets, or Android SDK and ADB for Android targets. Device, simulator, emulator, TV, macOS, or Linux desktop target that the agent is allowed to automate. Required local permissions such as Android device trust, iOS Developer Mode, macOS Accessibility, and Screen Recording where applicable.	Node.js installed for the MCP server. Chrome or compatible Chromium browser. BrowserMCP extension installed from the project site. MCP client such as Claude, Cursor, VS Code, Windsurf, or another compatible host.	Node.js 20.19.0 or newer. Local Firefox 100 or newer, or an explicit Firefox binary path passed through the documented CLI option. A dedicated Firefox automation profile with no personal cookies, saved passwords, or regular browsing sessions. Optional adb and Firefox for Android setup when using Android automation mode.
Install	claude mcp add zyntra-mail --transport http https://mcp.zyntra.app/mcp Copy install	claude mcp add --transport stdio --scope user agent-device -- agent-device mcp Copy install	npx @browsermcp/mcp@latest Copy install	npx -y firefox-devtools-mcp@latest Copy install
Config	{ "mcpServers": { "zyntra-mail": { "type": "http", "url": "https://mcp.zyntra.app/mcp", "headers": { "X-API-Key": "YOUR_API_KEY" } } } } Copy config	{ "mcpServers": { "agent-device": { "command": "agent-device", "args": ["mcp"] } } } Copy config	{ "mcpServers": { "browsermcp": { "command": "npx", "args": ["@browsermcp/mcp@latest"] } } } Copy config	{ "mcpServers": { "firefox-devtools": { "command": "npx", "args": [ "-y", "firefox-devtools-mcp@latest", "--headless", "--viewport", "1280x720" ], "env": { "START_URL": "about:home", "FIREFOX_HEADLESS": "true" } } } } Copy config
Citations	Source repositorygithub.com 2026-04-30T12:14:24.000Z Documentationdocs.zyntra.app Reviewed by JSONbored2026-04-30T12:14:24.000Z Submitted by dd77ss2026-04-28T18:34:47.000Z Source methodology →	Source repositorygithub.com 2026-07-04T21:34:14+00:00 Documentationgithub.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-04T21:34:14+00:00 Documentationdocs.browsermcp.io Submitted by oktofeesh12026-06-05 Source methodology →	Source repositorygithub.com 2026-07-04T21:34:14+00:00 Documentationgithub.com Submitted by oktofeesh12026-06-06 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Source-backed guides for putting this to work.

• Best list: MCP servers for browser automation