mcp server
Mailcannon
AI-powered email outreach platform — send campaigns with deliverability tracking.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Most recent push to the repository was 2026-07-31.
What this server can do
34 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
add_campaign_step(day, body, subject, campaignId)- Add a sequence step (delay in hours, subject, body) Required: campaignId, day, subject, body.
add_contact(tags, email, title, company, lastName, firstName)- Add a single contact Required: email, firstName.
add_contacts(contacts)- Bulk add contacts (max 100) Required: contacts.
add_provider(env, url, args, kind, name, command, transport)- Add an email provider Required: name, kind.
check_domain_deliverability(domain)- Check SPF, DKIM, DMARC records for a domain Required: domain.
check_email_spam_score(body, subject)- Analyze email subject/body for spam trigger words Required: subject, body.
check_step_spam_score(stepId)- Check a campaign step's subject and body for spam triggers Required: stepId.
create_campaign(name)- Create a new email campaign Required: name.
create_task(title, dueDate, priority, description)- Create a new task Required: title.
delete_campaign(id)- Delete a campaign and all its steps Required: id.
delete_campaign_step(id)- Delete a step from a campaign Required: id.
delete_task(id)- Delete a task by ID Required: id.
get_deliverability- Get deliverability stats (sent, opens, bounces, replies)
get_setting(key)- Get a user setting (e.g. timezone) Required: key.
list_campaigns- List all campaigns with their steps
list_contacts- List all contacts
list_providers- List all email providers
list_schedules- List all scheduled campaign runs
list_settings- List all user settings
list_tags- List all unique tags across your contacts
list_tasks- List all tasks
pause_campaign(id)- Pause a campaign — stops processing all active schedules for this campaign Required: id.
process_campaigns(includeFailed)- Process all due campaign schedules (includeFailed: true to retry failed ones)
remove_contact(id)- Remove a contact by ID Required: id.
remove_provider(id)- Remove a provider by ID Required: id.
resume_campaign(id)- Resume a paused campaign — reactivates all paused schedules Required: id.
retry_failed- Reset all failed schedules to active for retry
schedule_campaign(tags, startAt, campaignId, contactIds, providerId)- Assign contacts to a campaign and schedule it Required: campaignId.
send_test_email(body, subject, providerId)- Send a test email to yourself to preview formatting Required: subject, body.
set_setting(key, value)- Set a user setting (e.g. timezone to 'America/New_York') Required: key, value.
update_campaign(id, name)- Update a campaign's name Required: id, name.
update_campaign_step(id, day, body, subject)- Update a campaign step's day, subject, or body Required: id.
update_contact_tags(id, tags)- Set tags on a contact (replaces all tags) Required: id, tags.
update_task(id, title, status, dueDate, priority, description)- Update a task's status, priority, or fields Required: id.
Last successful function declaration observed on . Source: https://www.thinkandautomate.dev/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.thinkandautomate.dev/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-31 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-25 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-25 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 34 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.thinkandautomate.dev | |
| mcp endpoint status | ok | The server listed 34 functions when asked. | as of probe | www.thinkandautomate.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json