Email MCP Server

Created By
egyptianego17a year ago
A simple mcp server that lets your AI agent send emails and attach files through SMTP.
Overview

What is Email MCP Server?

Email MCP Server is a simple Model Context Protocol (MCP) server that enables your AI agent to send emails and attach files through SMTP.

How to use Email MCP Server?

To use Email MCP Server, install the required software, set up your SMTP configuration, and run the server. You can then send emails using simple commands or advanced features.

Key features of Email MCP Server?

  • Send plain text and HTML emails
  • Attach files and documents
  • Send emails to multiple recipients with CC/BCC
  • Test your email setup before sending

Use cases of Email MCP Server?

  1. Automating email notifications for project updates.
  2. Sending reports and documents to team members.
  3. Testing email configurations for various providers.

FAQ from Email MCP Server?

  • Can I use Email MCP Server with any email provider?

Yes! You can configure it with any SMTP server, including Gmail and Outlook.

  • Is there a limit on the number of emails I can send?

No, but be mindful of your email provider's sending limits.

  • How do I troubleshoot connection issues?

Check your SMTP settings, ensure your internet connection is stable, and verify that the required ports are open.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
egyptianego17
Star
0
Language
Python
License
MIT 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