One URL, one key. That's the install.
Paste the config into your client, drop in an API key from your Sender Pools account, and the 52 tools show up. The key fixes the account, so no tool ever asks for an account id.
- Create an API key in your Sender Pools account.
- Add the server to your client with the config on the right.
- Ask "who am I authenticated as?" to confirm it's wired up.
https://api.senderpools.com/api/mcp
{
"mcpServers": {
"sender-pools": {
"url": "https://api.senderpools.com/api/mcp",
"headers": {
"Authorization": "Bearer apiKey_YOUR_KEY"
}
}
}
}{
"mcpServers": {
"sender-pools": {
"url": "https://api.senderpools.com/api/mcp",
"headers": {
"Authorization": "Bearer apiKey_YOUR_KEY"
}
}
}
}claude mcp add --transport http sender-pools https://api.senderpools.com/api/mcp \
--header "Authorization: Bearer apiKey_YOUR_KEY"Things that used to be twelve clicks are now one sentence.
Every prompt below runs against the live server. Copy one, paste it into your agent, swap in your ICP name.
Import a list and launch it
Point the agent at a CSV. It previews how many are already in the ICP, imports the rest with tags, timezone and weekend rules, then schedules the start date and daily lead cap. Big lists finish in the background.
Write a variant, test it, keep the winner
Multiple variants on a step run as a random-split A/B test. The agent can draft one, preview it against a real prospect with tokens and spintax resolved, read per-variant reply rates, retire the loser and rebuild the queued emails.
Triage replies without opening a tab
Filter threads by replied, unread, out-of-office or archived. Pull a full thread, override a lead classification, reply from the mailbox that sent the original, or forward it to a colleague with a covering note.
Ask across every workspace at once
Read tools accept all as the workspace id, so credit balances, mailbox reputation and daily send capacity come back for the whole account in one call. Agencies, this one's for you.
52 tools. The whole product, nothing held back.
If you can do it in the app, the agent can do it too. Nearly every tool takes a workspace id; read tools accept all. The account is fixed by your key.
Account & workspaces
6 tools- Who does this key authenticate as, plus account details
- List workspaces with credit balances; get one with its ICPs and tags
- Mailbox counts and health; workspace-wide daily send metrics with capacity
Tool names
get_current_userget_accountlist_workspacesget_workspaceget_mailbox_metricsget_workspace_send_metrics
ICPs (sending programs)
7 tools- List, get, create and update ICPs; create queues AI enrichment of problem, solution, status quo and competitive advantage
- Pause and resume, schedule a start date, set days between sends and max new leads per day
- Unsubscribe on reply, auto-pause on company reply
- Cumulative metrics, daily send metrics, sends still queued per mailbox type
Tool names
list_icpsget_icpcreate_icpupdate_icpget_icp_metricsget_icp_send_metrics_by_dayget_icp_sends_remaining
Contacts & prospects
13 tools- Import into an ICP with tags, timezone, sending strategy and weekend rules; duplicates skipped, large imports finish in the background
- Preview how many of a list are already in the ICP
- List, search, batch update, unsubscribe, bulk tag or DNC, delete
- List prospects by lead response and reply date; override a classification; remove from an ICP
- Import history, tags and custom fields (create up to 25 per workspace)
Tool names
import_contactspreview_import_deduplicationlist_contactsupdate_contactsdelete_contactstag_or_dnc_contactslist_icp_prospectsset_prospect_lead_responseremove_icp_prospectslist_importslist_contact_tagslist_custom_fieldscreate_custom_field
Do-not-contact
3 tools- List DNC entries
- Add by email or whole domain
- Remove entries
Tool names
list_dnc_entriesadd_dnc_entriesremove_dnc_entries
Sequences & copy
10 tools- Configure step count and whether each step is AI-written or template-based
- Get and update one step, including delay override and reply-in-thread
- Create, update, retire and delete email templates; multiple templates on a step run as a random-split A/B test
- Preview copy against a real prospect with tokens and spintax resolved
- Per-template sends and reply rates; rebuild queued emails after copy changes
- Generated copy and delivery status of any single sent email
Tool names
configure_sequenceget_sequence_stepupdate_sequence_stepcreate_email_templateupdate_email_templatedelete_email_templatepreview_email_copyget_template_metricsrebuild_step_emailsget_crafted_email
Inbox & mailboxes
6 tools- List threads filtered by replies, unread, out-of-office and archived
- Get a full thread, reply from one of your mailboxes, forward with a covering note
- List mailboxes; get one with its reputation score
Tool names
list_inbox_threadsget_inbox_threadreply_to_threadforward_messagelist_mailboxesget_mailbox
Webhooks
7 tools- List, create, update and delete endpoints with event type and lead response filters
- Send a test event
- Regenerate the signing secret, read the delivery log
Tool names
list_webhook_endpointscreate_webhook_endpointupdate_webhook_endpointdelete_webhook_endpointsend_webhook_test_eventregenerate_webhook_secretlist_webhook_deliveries
Key-scoped, not account-scoped
The key authenticates the account. No tool takes an account id, so agents can't wander into someone else's data.
One call spans the account
Every read tool accepts all. Write tools stay pinned to one workspace so nothing bulk-edits by accident.
Safe on big lists
Duplicates are skipped, large imports finish in the background, and you can preview overlap before committing anything.
- Does Sender Pools have an API?
- Yes. The public REST API is documented at https://sender-pools.readme.io and authenticates with a bearer API key. It covers workspaces, ICPs, contacts, sequences and copy, the inbox, mailboxes, do-not-contact lists and webhooks.
- What is the Sender Pools MCP server?
- The Sender Pools MCP server lets an AI agent such as Claude, Cursor or Claude Code operate your account in plain English. It exposes 52 tools covering everything in the product: import lists, create and schedule ICPs, write and A/B test copy, triage the inbox, watch mailbox health and manage webhooks. It runs over Streamable HTTP at https://api.senderpools.com/api/mcp, so there is nothing to install locally. Setup instructions are at https://senderpools.com/mcp.
- How do I connect the MCP server?
- Create an API key in your Sender Pools account, then add the server to your MCP client with the URL https://api.senderpools.com/api/mcp and an Authorization header of "Bearer <your API key>". In Claude Code that is one command: claude mcp add --transport http sender-pools https://api.senderpools.com/api/mcp --header "Authorization: Bearer <your API key>". Ask the agent "who am I authenticated as?" to confirm.
- What can an agent connected over MCP access?
- Only the account the API key belongs to. No tool takes an account id, so an agent cannot reach another customer's data. Read tools accept the literal workspace id "all" to span every workspace in the account; write tools are pinned to a single workspace so nothing bulk-edits by accident.
- Which MCP clients work with it?
- Any client that speaks Streamable HTTP MCP, including Claude Desktop, Claude Code and Cursor. The server exposes tools only, with no resources or prompts.