Emitd MCP Server
com.emitdPublished by emitd.comOfficial publisherv1.0.1Updated Nov 1, 2026
Connect AI agents to Emitd email sending, message tracking, templates, and automations.
Overview
Hosted Emitd MCP endpoint that lets an assistant send and track email, use templates, and manage contacts, domains and automations.
- What you can do
- Send single or batch email, with dry-run validation and duplicate protection
- Look up messages and delivery activity, and read inbound email
- List and use templates, sending domains, contacts, audiences and segments
- Work with broadcasts, automations, webhooks, suppressions and analytics
- When to use it
- Useful when an agent should send transactional or campaign email through an Emitd account, reuse existing templates, or check whether a message was delivered, without building a custom API integration.
- Requirements
- A remote MCP endpoint at mcp.emitd.com over streamable HTTP; an Emitd account and an API key created in the Emitd console, supplied as an Authorization Bearer header. Available tools depend on the key's permissions and enabled features.
Installation
In SourceWeft
- Open Emitd MCP Server in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.emitd%2Femitd/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"emitd": {
"type": "http",
"url": "https://mcp.emitd.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
Emitd MCP Server
Connect AI agents and MCP-compatible clients to Emitd's hosted email platform through the Model Context Protocol (MCP).
- Website: https://emitd.com
- MCP documentation: https://docs.emitd.com/docs/guides/agents
- Hosted MCP endpoint: https://mcp.emitd.com/mcp
- Authentication: Emitd API key sent as
Authorization: Bearer <API_KEY>
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
- Sign in to the Emitd console: https://app.emitd.com
- Create an API key with only the permissions required for your agent.
- Configure your MCP-compatible client to connect to
https://mcp.emitd.com/mcp. - Supply the API key using the
Authorization: Bearer <API_KEY>header through the client's supported secret configuration. - 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:
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:
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.
Source: README.md at commit aa01415
Tools
0Version history
1- v1.0.1LatestOct 25, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts