Mcp Server Tempmail

Created By
Selenium399 months ago
An MCP (Model Context Protocol) server for temporary email management using the ChatTempMail API.
Overview

what is Mcp Server Tempmail?

Mcp Server Tempmail is an MCP (Model Context Protocol) server designed for managing temporary email addresses using the ChatTempMail API.

how to use Mcp Server Tempmail?

To use Mcp Server Tempmail, you need to obtain an API key from chat-tempmail.com, configure your MCP client with the API key, and then restart the application.

key features of Mcp Server Tempmail?

  • Get available email domains
  • Create temporary email addresses
  • List and delete emails
  • Retrieve and view email messages
  • Configure webhooks for email notifications

use cases of Mcp Server Tempmail?

  1. Creating temporary email addresses for one-time registrations.
  2. Managing multiple temporary emails for testing purposes.
  3. Receiving and viewing messages sent to temporary emails without revealing personal information.

FAQ from Mcp Server Tempmail?

  • How do I get an API key?

Visit chat-tempmail.com, register, and create an API key in your profile.

  • Can I customize the base URL?

Yes, you can set the TEMPMAIL_BASE_URL environment variable to customize it.

  • What happens to temporary emails after their expiry time?

Temporary emails will automatically expire based on the set expiry time.

Server Config

{
  "mcpServers": {
    "tempmail": {
      "command": "npx",
      "args": [
        "mcp-server-tempmail"
      ],
      "env": {
        "TEMPMAIL_API_KEY": "your-api-key-here",
        "TEMPMAIL_BASE_URL": "https://chat-tempmail.com"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Selenium39
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago