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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago