Skip to content

MCP server

Connect Claude, ChatGPT, Cursor or any app that speaks the Model Context Protocol to your Sendwing workspace. Ask it to draft a campaign, build a workflow, tidy your contacts or explain last week’s results.

https://mcp.sendwing.app

One hosted server, over the Streamable HTTP transport. There’s nothing to install and no API key: you add the URL to your app, then sign in with OAuth when it asks. Until you sign in, every request gets 401 Unauthorized.

Adding the server and signing in are two steps in every app. The fastest way to add it to coding agents is one command, which finds the agents on your machine and asks which to set up:

Terminal window
npx add-mcp https://mcp.sendwing.app

Or set up one app yourself:

Terminal window
claude mcp add --transport http sendwing https://mcp.sendwing.app

Then run /mcp in Claude Code, choose sendwing and Authenticate.

  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it Sendwing and paste the server URL.
  3. Choose Connect, sign in to Sendwing, pick the workspace and approve what Claude may do there.

Add Sendwing to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
"mcpServers": {
"sendwing": {
"url": "https://mcp.sendwing.app"
}
}
}

Then open Cursor Settings → MCP, find sendwing and choose the button to log in.

Add Sendwing to .vscode/mcp.json in your project, or to your user configuration with MCP: Open User Configuration:

{
"servers": {
"sendwing": {
"type": "http",
"url": "https://mcp.sendwing.app"
}
}
}

Choose Start above the server, trust it when asked, and sign in when VS Code opens your browser.

Add Sendwing to ~/.codex/config.toml:

[mcp_servers.sendwing]
url = "https://mcp.sendwing.app"

Then sign in:

Terminal window
codex mcp login sendwing
  1. Open Settings → Apps & Connectors. Under Advanced settings, turn on Developer mode.
  2. Choose Create, name it Sendwing, paste the server URL and choose OAuth for authentication.
  3. Sign in to Sendwing when ChatGPT asks, then add the app to a chat from the + menu.

Add Sendwing to ~/.codeium/windsurf/mcp_config.json, then refresh the MCP servers in Cascade and sign in:

{
"mcpServers": {
"sendwing": {
"serverUrl": "https://mcp.sendwing.app"
}
}
}
Terminal window
gemini mcp add --transport http sendwing https://mcp.sendwing.app

Then run /mcp auth sendwing in Gemini CLI.

Look for a setting to add a remote or custom MCP server, paste the server URL, and choose OAuth if it asks how to authenticate. Apps that support remote servers with OAuth find Sendwing’s sign-in page and register themselves; there’s no client ID to ask for.

Ask your app:

What’s in my Sendwing workspace? List my sending domains, mailing lists and the last five campaigns.

If it answers from your workspace, you’re connected. If the app shows Needs authentication or a 401, sign in again from its MCP settings.

  1. Your browser opens Sendwing. Sign in if you aren’t already.
  2. Pick one workspace. The app can see and change only that one.
  3. Approve the permissions it asks for. It can then do only what both those permissions and your role in the workspace allow.

At first the app is offered everything except actions that email people or delete contacts. Those ask again the first time they’re needed, so sending is always a separate yes.

A connection never covers billing, your team, API keys, exporting every contact, changing how the workspace sends, or emailing addresses outside a campaign or test. The app stays signed in while it’s used: its access renews itself, for up to 90 days between uses. See and disconnect apps under Settings → Connected apps, which stops the app at once.

ScopeAllows
contacts:readRead contacts, custom properties, tags, mailing lists and segments
contacts:writeAdd and change contacts, their tags, lists, subscription and events
contacts:deleteDelete contacts and every record of them (asked for when first needed)
audience:writeCreate, change and delete custom properties, tags, mailing lists and segments
templates:readRead templates
templates:writeCreate, change and delete templates
campaigns:readRead campaigns and their reports
campaigns:writeCreate, change and delete draft campaigns
campaigns:sendSend, schedule and cancel campaigns, and send tests (asked for when first needed)
workflows:readRead workflows and their reports
workflows:writeCreate, change and archive workflows
workflows:publishPublish, pause and resume workflows, and enroll contacts (asked for when first needed)
domains:readRead sending domains and sending settings
domains:writeAdd, verify and remove sending domains

You don’t need this to connect; it helps when an app won’t. Sendwing follows the MCP authorization spec:

  1. The app calls https://mcp.sendwing.app and gets 401 with a WWW-Authenticate header pointing to the server’s metadata at /.well-known/oauth-protected-resource.
  2. That metadata names the authorization server, https://api.sendwing.app/api/auth, whose own metadata lists its endpoints.
  3. The app registers itself, by dynamic client registration or a client ID metadata document.
  4. It opens your browser to sign in and approve, using the authorization code flow with PKCE (S256).
  5. It exchanges the code for an access token, which lasts an hour, and a refresh token, which keeps it signed in.

62 tools. Each is marked as read-only, a change, or destructive (it can’t be undone), and tools that email people say so, so apps can ask before running them. Your app lists them too, with their inputs.

Contacts

ToolWhat it does
list_contactsList contacts, newest first
get_contactGet one contact with its fields, tags and lists
upsert_contactCreate a contact, or update the one with the same email or external id
update_contactChange a contact’s fields or subscription
delete_contactDelete a contact and its history Destructive
list_contact_timelineList what happened to a contact: emails, opens, clicks, events
list_contact_propertiesList the workspace’s custom properties
create_contact_propertyAdd a custom property
update_contact_propertyRename or change a custom property
delete_contact_propertyDelete a custom property and its values Destructive
record_eventsRecord named events on contacts; starts workflows triggered by them

Tags, lists and segments

ToolWhat it does
list_tagsList tags
create_tagCreate a tag
tag_contactsAdd or remove a tag on contacts
list_mailing_listsList mailing lists
create_mailing_listCreate a mailing list
update_list_subscriptionsSubscribe or unsubscribe contacts from a list
list_segmentsList segments
get_segmentGet a segment and its filter
list_segment_contactsList the contacts a segment matches
preview_segmentCount the contacts a filter would match, saving nothing
create_segmentSave a filter as a segment
update_segmentChange a segment
delete_segmentDelete a segment Destructive

Templates and campaigns

ToolWhat it does
list_templatesList email templates
get_templateGet a template’s content
create_templateCreate a template from markdown
update_templateChange a template
send_template_testSend a test of a template to up to 5 addresses Sends email
preview_emailRender markdown as the HTML and text a recipient gets, saving nothing
list_campaignsList campaigns
get_campaignGet a campaign’s settings, status and content
create_campaignCreate a draft campaign
update_campaignChange a draft campaign
get_campaign_checklistCheck whether a campaign is ready to send
send_campaign_testSend a test of a campaign to up to 5 addresses Sends email
send_campaignSend a campaign to its audience now, or schedule it Destructive Sends email
unschedule_campaignTurn a scheduled campaign back into a draft
cancel_campaignStop a scheduled or sending campaign for good Destructive
get_campaign_reportGet a campaign’s delivery, opens, clicks and bounces

Workflows

ToolWhat it does
list_workflowsList workflows
get_workflowGet a workflow’s document and status
create_workflowCreate a draft workflow from a document
update_workflowChange a workflow’s draft
check_workflowCheck a draft and what publishing it would do
publish_workflowPublish a draft: contacts start entering it Destructive Sends email
get_workflow_reportGet each step’s delivery, opens, clicks and bounces
list_workflow_email_recipientsList who a workflow email went to
get_workflow_email_timelineGet a workflow email’s opens and clicks over time
enroll_contacts_in_workflowPut contacts into an active workflow at its start Sends email
pause_workflowPause a workflow
resume_workflowResume a paused workflow
archive_workflowStop a workflow for good Destructive
send_workflow_email_testSend a test of a workflow email Sends email

Sending domains

ToolWhat it does
get_sending_settingsGet the workspace’s sending settings
list_sending_domainsList sending domains
get_sending_domainGet a domain and its DNS records
add_sending_domainAdd a domain to send from; returns the DNS records to publish
verify_sending_domainCheck a domain’s DNS records
get_sending_domain_linkGet a shareable link to a domain’s DNS records
email_sending_domain_recordsEmail a domain’s DNS records to whoever manages DNS Sends email

Guides

ToolWhat it does
get_guideRead how to write an email, workflow or segment for Sendwing

The guides are also MCP resources, at sendwing://guides/email, sendwing://guides/workflow and sendwing://guides/segment.

  • Consent is enforced by Sendwing, not the AI. A contact who unsubscribed themselves can only be subscribed again by themselves; the server refuses it.
  • The legal footer stays. Every email gets your address and an unsubscribe link, whatever the AI writes.
  • One workspace per connection. An app connected to one workspace can’t see another.
  • “Draft a campaign announcing our October update to the Newsletter list and send me a test.”
  • “Set up a welcome workflow that emails new contacts when they sign up and follows up three days later.”
  • “Make a segment of contacts in Germany who opened an email in the last 30 days.”
  • “Add mail.example.com as a sending domain and email its DNS records to dns@example.com.”

From start to finish:

Check that our sending domain is verified. Then draft a campaign to the Newsletter list announcing our new pricing, using the email guide, and send a test to me. Don’t send it to the list until I’ve read the test.

For questions about results, see Ask about your results.

What you see What to do
Needs authentication, or 401 Sign in from the app’s MCP settings. If it keeps asking, remove the server and add it again.
The wrong workspace A connection covers one workspace. Disconnect the app under Settings → Connected apps, then sign in again and pick the other one.
A tool says it lacks permission Approve the permission when the app asks, or reconnect and approve it. Your role in the workspace can also limit what a connection does.
Tools are missing Some apps let you turn tools off; check the server’s tool list in the app.
The app can’t connect at all It needs remote MCP servers with OAuth. Apps that only run local servers can’t connect.

The server reads and changes your workspace only through the tools above, as the API would. It sees only the tool calls the AI makes, never your conversation. What Sendwing stores is covered by the Privacy Policy, and what you may send by the Acceptable Use Policy.

Questions or a tool that misbehaves: support@sendwing.app. The same actions are available over the REST API.