Skip to main content
Glama

Emitd MCP Server

Server Details

Connect AI agents to Emitd email sending, message tracking, templates, and automations. Emitd hosts a Model Context Protocol server for integrating supported email operations into AI-agent workflows. Connect a compatible client to the hosted endpoint (https://mcp.emitd.com/mcp) and authenticate with an Emitd API key. Available tools depend on the key's permissions and enabled features. Emitd's capability areas include sending email, message activity, templates, contacts, audiences, segments, domains, analytics, inbound email, broadcasts, automations, webhooks, and suppressions. Use restricted keys, sending guardrails, and approval settings appropriate to each workflow. For more information check https://emitd.com

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
tponnam/emitd-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

Each tool maps to a distinct stage of the send pipeline: validate an address, check a draft, send one, send many. The only mild overlap is check_email vs validate_email, since both are 'check before sending' tools, but their descriptions clearly separate content checks from address deliverability.

Naming Consistency5/5

All four names follow the same snake_case verb_noun pattern (check_email, send_batch, send_email, validate_email) with verbs that accurately describe the action. No mixed conventions or vague verbs anywhere in the set.

Tool Count5/5

Four tools is tightly scoped to the domain: pre-send validation, draft linting, single send, and batch send. Nothing is redundant and each tool earns its place in the workflow.

Completeness3/5

The core send lifecycle is covered, but send_email explicitly points to list_domains, which is not in this tool surface — a dead reference an agent will trip over. Template usage is also described (template_alias/template_model) with no tool to list or inspect available templates, and there is no way to look up message status after a send.

Publisher details

Operator
https://emitd.com · Publisher source
Vendor relationship
Not applicable
Trust center
Not applicable
Restrictions
Unknown

Available Tools

4 tools
check_emailCheck an email before sendingB
Idempotent
Inspect

Reads a draft for mistakes that can't be taken back: links or images on a local address, unfilled {{placeholders}}, links that go nowhere, missing alt text, HTML big enough for Gmail to clip. Sends nothing and fetches nothing. Use it before send_email when you wrote or changed the HTML yourself, and fix every finding with severity error.

Inputs: subject, html_body, text_body.

send_batchSend up to 100 emailsA
Destructive
Inspect

Send up to 100 independent emails in one call; each item has send_email's fields. Results come back per email, in input order. Same dry_run and duplicate protection as send_email, applied to the whole batch. If this key's guardrails need a person, the call either asks them in chat once for the whole batch, or returns status pending_approval with an approval_url on each email that waits.

Inputs: emails (required), dry_run, allow_duplicate, idempotency_key.

send_emailSend an emailAInspect

Send one email from an address on a verified domain (see list_domains). Give html_body and/or text_body, or template_alias plus template_model to render a saved template. Use dry_run: true to validate a new or uncertain send without delivering it. An identical send within 10 minutes returns the original message_id instead of sending again; pass idempotency_key to control that, or allow_duplicate: true to send another copy on purpose. Returns message_id and status. If this key's guardrails need a person, the call either asks them in chat or returns status pending_approval with an approval_url to share.

Inputs: from (required), cc, to, bcc, +18 more.

validate_emailValidate an email addressA
Idempotent
Inspect

Check one address before adding it as a contact or sending to a newly collected address. result is deliverable, risky (disposable, random-looking, or no MX record), undeliverable (bad syntax, no such domain, no mail server, or a previous hard bounce — do not send), or unknown (DNS unreadable right now; retry later). did_you_mean carries a corrected address when the domain looks like a typo — offer it to the user rather than sending to the original. 1,000 checks per workspace per day.

Inputs: email (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to send and manage email, read threaded replies, run campaigns and automations, and handle approvals through the Model Context Protocol from any compatible client.
      45
      531 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to send, receive, and track email and manage templates, domains, webhooks, and other email API operations from AI assistants.
      374 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      The email API your AI agent can actually use. A Model Context Protocol server for Send16 that gives Claude, Cursor, and any MCP client 79 tools to send transactional & marketing email, manage contacts, audiences, segments, automations, templates, the inbox, suppressions, and webhooks.
      79
      68 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.
      11
      13 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.