email mcp

Created By
caijianying7 months ago
这是一个基于 MCP 协议的邮件发送服务
Overview

what is Email-MCP?

Email-MCP is a mail sending service based on the MCP protocol, allowing AI assistants to automatically send emails through a standardized interface.

how to use Email-MCP?

To use Email-MCP, clone the repository, install dependencies, build the project, and configure it to run locally. You can then interact with the AI assistant to send emails by providing required parameters such as SMTP server details and email content.

key features of Email-MCP?

  • Standardized interface for email sending via AI assistants
  • Supports any AI assistant that complies with the MCP protocol
  • Local environment setup for testing and development

use cases of Email-MCP?

  1. Automating email responses through AI assistants
  2. Integrating email functionalities into AI-driven applications
  3. Sending notifications or alerts via email from AI systems

FAQ from Email-MCP?

  • What is the MCP protocol?

The MCP protocol is a standardized communication protocol for AI assistants to interact with various services.

  • Can I use Email-MCP in a production environment?

Currently, Email-MCP is only tested for local environments.

  • How do I configure the SMTP server?

You need to provide the SMTP server hostname, port, sender email, password, recipient email, subject, and body of the email.

Server Config

{
  "mcpServers": {
    "email-mcp": {
      "command": "node",
      "args": [
        "yourpath\\email-mcp\\build\\server.js",
        "--verbose"
      ],
      "env": {}
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
caijianying
Star
-
Language
-
License
-
Category

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
Tavily Mcp
@tavily-ai

JavaScript
a year ago