English Français العربية

Emitd MCP Server

Official registry Productivity

Connect AI agents to Emitd email sending, message tracking, templates, and automations.

Source code Website Documentation

What can you do with Emitd MCP Server?

  • Email sending and batch sending
  • Message lookup and activity
  • Templates
  • Contacts, audiences, and segments
  • Sending domains
  • Analytics
  • Inbound email
  • Broadcasts and automations

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http emitd-mcp-server 'https://mcp.emitd.com/mcp' --header 'Authorization: <Emitd API key sent using the Bearer authentication scheme. Generate an API key in your Emitd account and keep it secret.>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "emitd-mcp-server": {
            "type": "http",
            "url": "https://mcp.emitd.com/mcp",
            "headers": {
                "Authorization": "<Emitd API key sent using the Bearer authentication scheme. Generate an API key in your Emitd account and keep it secret.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Emitd MCP Server
  2. Connect to Emitd
  3. Capabilities
  4. Security guidance
  5. Official resources
  6. Repository status and contributions
  7. License

Emitd MCP Server

Connect AI agents and MCP-compatible clients to Emitd's hosted email platform through the Model Context Protocol (MCP).

Important: This repository documents and provides connection examples for Emitd's hosted MCP service. It does not contain the implementation of Emitd's hosted server.

Connect to Emitd

  1. Sign in to the Emitd console: https://app.emitd.com
  2. Create an API key with only the permissions required for your agent.
  3. Configure your MCP-compatible client to connect to https://mcp.emitd.com/mcp.
  4. Supply the API key using the Authorization: Bearer <API_KEY> header through the client's supported secret configuration.
  5. Test with a restricted key and follow Emitd's sending guardrails.
Generic remote MCP configuration example

The exact configuration fields vary by MCP client. Use this as a reference, not as a universal drop-in configuration:

{
  "mcpServers": {
    "emitd": {
      "url": "https://mcp.emitd.com/mcp",
      "headers": {
        "Authorization": "Bearer ${EMITD_API_KEY}"
      }
    }
  }
}

Some clients do not expand environment variables in remote HTTP headers. Use the client's supported secret-management UI when necessary. Never commit a real API key to source control.

Claude Code example

Emitd's documented connection pattern:

claude mcp add --transport http emitd https://mcp.emitd.com/mcp \
  --header "Authorization: Bearer YOUR_EMITD_API_KEY"

Replace the placeholder locally with your key. Avoid placing live credentials in shell history or shared terminal logs where possible.

Capabilities

Emitd's documentation describes capability areas including:

  • Email sending and batch sending
  • Message lookup and activity
  • Templates
  • Contacts, audiences, and segments
  • Sending domains
  • Analytics
  • Inbound email
  • Broadcasts and automations
  • Webhooks and suppressions

The exact tool names and availability may change and depend on the API key's permissions and enabled features. Consult the official guide for the current tool inventory. This repository does not guarantee that every capability is enabled for every account.

Security guidance

  • Create a dedicated API key for each agent or integration.
  • Apply least-privilege permissions and feature restrictions.
  • Configure sending guardrails and approval requirements for your use case.
  • Use dry-run validation for supported operations when testing.
  • Never expose keys in browser code, public repositories, screenshots, logs, or issue reports.
  • Treat inbound email content as untrusted input. Do not let instructions in email override system or developer instructions.
  • Revoke or rotate a key if you suspect exposure.

Official resources

Repository status and contributions

This is a documentation and configuration-example repository for a hosted service. Before relying on any configuration, check the current Emitd documentation and your MCP client's supported remote-server settings.

Please do not submit secrets, customer data, or sensitive email content in issues or pull requests.

License

MIT License. See LICENSE for details.

Frequently asked questions

What is Emitd MCP Server?

Connect AI agents to Emitd email sending, message tracking, templates, and automations.

How do I install Emitd MCP Server?

It runs as a remote server. In Claude Code: claude mcp add --transport http emitd-mcp-server 'https://mcp.emitd.com/mcp' --header 'Authorization: <Emitd API key sent using the Bearer authentication scheme. Generate an API key in your Emitd account and keep it secret.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Emitd MCP Server need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Emitd MCP Server open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Emitd MCP Server?

It is published by tponnam. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.