
Senders Mcp
io.github.dame-sendersPublished by GitHub account dame-sendersv1.0.0Updated Oct 25, 2026
Cold email infrastructure — campaigns, prospects, mailbox health and replies via Claude.
Overview
A remote MCP endpoint for cold email infrastructure that lets an assistant work with campaigns, prospects, mailbox health and replies.
- What you can do
- Work with cold email campaigns through the assistant, per the registry description, which names campaigns as one area it covers. Handle prospects, the people targeted by outreach. Check mailbox health for the sending accounts. Deal with replies to outreach. No tool list is published, so the exact operations available are not documented here.
- When to use it
- Useful when you run cold email outreach and want an assistant to help manage campaigns, prospects, mailbox health or replies without leaving the conversation. Less relevant if you do not use this provider's email infrastructure.
- Requirements
- A remote MCP endpoint reached over streamable HTTP at the provider's hosted address; no local package is needed. The manifest declares no authentication, environment variables or headers, so any account or sign-in requirement is not documented here.
Installation
In SourceWeft
- Open Senders Mcp in the dashboard and add it to a workspace.
- 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/io.github.dame-senders%2Fsenders-mcp/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": {
"senders": {
"type": "http",
"url": "https://mcp.senders.ai/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
60% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.