mcp-email-docker

Created By
fantasy-lotusa year ago
基于Typescript实现的Notify MCP Server,支持Docker一键部署到remote|local
Overview

What is mcp-email-docker?

mcp-email-docker is a mail notification service based on the Model Context Protocol (MCP), designed to facilitate communication between clients and servers using Streamable HTTP and Server-Sent Events (SSE). It supports Docker for easy deployment.

How to use mcp-email-docker?

To use mcp-email-docker, install the dependencies, configure the environment variables, and either run it locally or deploy it using Docker.

Key features of mcp-email-docker?

  • Integrates with MCP Clients to send emails or notifications via the MCP protocol.
  • Compatible with both old SSE and new Streamable HTTP protocols.
  • Supports one-click Docker deployment to remote or local environments, using HTTP for communication.

Use cases of mcp-email-docker?

  1. Sending real-time email notifications to users.
  2. Implementing a notification system for web applications.
  3. Learning and experimenting with MCP server implementations.

FAQ from mcp-email-docker?

  • Can I deploy mcp-email-docker without Docker?

Yes, you can run it locally by following the setup instructions without Docker.

  • What protocols does mcp-email-docker support?

It supports Streamable HTTP and Server-Sent Events for real-time communication.

  • Is there a guide for setting up the environment?

Yes, the project includes a detailed guide for configuring environment variables and running the service.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fantasy-lotus
Star
1
Language
TypeScript
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.

8 hours ago