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.
Server URL
Section titled “Server URL”https://mcp.sendwing.appOne 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.
Connect a client
Section titled “Connect a client”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:
npx add-mcp https://mcp.sendwing.appOr set up one app yourself:
Claude Code
Section titled “Claude Code”claude mcp add --transport http sendwing https://mcp.sendwing.appThen run /mcp in Claude Code, choose sendwing and Authenticate.
Claude (claude.ai and Claude Desktop)
Section titled “Claude (claude.ai and Claude Desktop)”- Open Settings → Connectors and choose Add custom connector.
- Name it Sendwing and paste the server URL.
- Choose Connect, sign in to Sendwing, pick the workspace and approve what Claude may do there.
Cursor
Section titled “Cursor”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.
VS Code
Section titled “VS Code”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:
codex mcp login sendwingChatGPT
Section titled “ChatGPT”- Open Settings → Apps & Connectors. Under Advanced settings, turn on Developer mode.
- Choose Create, name it Sendwing, paste the server URL and choose OAuth for authentication.
- Sign in to Sendwing when ChatGPT asks, then add the app to a chat from the + menu.
Windsurf
Section titled “Windsurf”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" } }}Gemini CLI
Section titled “Gemini CLI”gemini mcp add --transport http sendwing https://mcp.sendwing.appThen run /mcp auth sendwing in Gemini CLI.
Any other app
Section titled “Any other app”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.
Check it works
Section titled “Check it works”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.
What happens when you sign in
Section titled “What happens when you sign in”- Your browser opens Sendwing. Sign in if you aren’t already.
- Pick one workspace. The app can see and change only that one.
- 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.
Permissions
Section titled “Permissions”| Scope | Allows |
|---|---|
contacts:read | Read contacts, custom properties, tags, mailing lists and segments |
contacts:write | Add and change contacts, their tags, lists, subscription and events |
contacts:delete | Delete contacts and every record of them (asked for when first needed) |
audience:write | Create, change and delete custom properties, tags, mailing lists and segments |
templates:read | Read templates |
templates:write | Create, change and delete templates |
campaigns:read | Read campaigns and their reports |
campaigns:write | Create, change and delete draft campaigns |
campaigns:send | Send, schedule and cancel campaigns, and send tests (asked for when first needed) |
workflows:read | Read workflows and their reports |
workflows:write | Create, change and archive workflows |
workflows:publish | Publish, pause and resume workflows, and enroll contacts (asked for when first needed) |
domains:read | Read sending domains and sending settings |
domains:write | Add, verify and remove sending domains |
How the handshake works
Section titled “How the handshake works”You don’t need this to connect; it helps when an app won’t. Sendwing follows the MCP authorization spec:
- The app calls
https://mcp.sendwing.appand gets401with aWWW-Authenticateheader pointing to the server’s metadata at/.well-known/oauth-protected-resource. - That metadata names the authorization server,
https://api.sendwing.app/api/auth, whose own metadata lists its endpoints. - The app registers itself, by dynamic client registration or a client ID metadata document.
- It opens your browser to sign in and approve, using the authorization code flow with PKCE (
S256). - 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
| Tool | What it does |
|---|---|
list_contacts | List contacts, newest first |
get_contact | Get one contact with its fields, tags and lists |
upsert_contact | Create a contact, or update the one with the same email or external id |
update_contact | Change a contact’s fields or subscription |
delete_contact | Delete a contact and its history Destructive |
list_contact_timeline | List what happened to a contact: emails, opens, clicks, events |
list_contact_properties | List the workspace’s custom properties |
create_contact_property | Add a custom property |
update_contact_property | Rename or change a custom property |
delete_contact_property | Delete a custom property and its values Destructive |
record_events | Record named events on contacts; starts workflows triggered by them |
Tags, lists and segments
| Tool | What it does |
|---|---|
list_tags | List tags |
create_tag | Create a tag |
tag_contacts | Add or remove a tag on contacts |
list_mailing_lists | List mailing lists |
create_mailing_list | Create a mailing list |
update_list_subscriptions | Subscribe or unsubscribe contacts from a list |
list_segments | List segments |
get_segment | Get a segment and its filter |
list_segment_contacts | List the contacts a segment matches |
preview_segment | Count the contacts a filter would match, saving nothing |
create_segment | Save a filter as a segment |
update_segment | Change a segment |
delete_segment | Delete a segment Destructive |
Templates and campaigns
| Tool | What it does |
|---|---|
list_templates | List email templates |
get_template | Get a template’s content |
create_template | Create a template from markdown |
update_template | Change a template |
send_template_test | Send a test of a template to up to 5 addresses Sends email |
preview_email | Render markdown as the HTML and text a recipient gets, saving nothing |
list_campaigns | List campaigns |
get_campaign | Get a campaign’s settings, status and content |
create_campaign | Create a draft campaign |
update_campaign | Change a draft campaign |
get_campaign_checklist | Check whether a campaign is ready to send |
send_campaign_test | Send a test of a campaign to up to 5 addresses Sends email |
send_campaign | Send a campaign to its audience now, or schedule it Destructive Sends email |
unschedule_campaign | Turn a scheduled campaign back into a draft |
cancel_campaign | Stop a scheduled or sending campaign for good Destructive |
get_campaign_report | Get a campaign’s delivery, opens, clicks and bounces |
Workflows
| Tool | What it does |
|---|---|
list_workflows | List workflows |
get_workflow | Get a workflow’s document and status |
create_workflow | Create a draft workflow from a document |
update_workflow | Change a workflow’s draft |
check_workflow | Check a draft and what publishing it would do |
publish_workflow | Publish a draft: contacts start entering it Destructive Sends email |
get_workflow_report | Get each step’s delivery, opens, clicks and bounces |
list_workflow_email_recipients | List who a workflow email went to |
get_workflow_email_timeline | Get a workflow email’s opens and clicks over time |
enroll_contacts_in_workflow | Put contacts into an active workflow at its start Sends email |
pause_workflow | Pause a workflow |
resume_workflow | Resume a paused workflow |
archive_workflow | Stop a workflow for good Destructive |
send_workflow_email_test | Send a test of a workflow email Sends email |
Sending domains
| Tool | What it does |
|---|---|
get_sending_settings | Get the workspace’s sending settings |
list_sending_domains | List sending domains |
get_sending_domain | Get a domain and its DNS records |
add_sending_domain | Add a domain to send from; returns the DNS records to publish |
verify_sending_domain | Check a domain’s DNS records |
get_sending_domain_link | Get a shareable link to a domain’s DNS records |
email_sending_domain_records | Email a domain’s DNS records to whoever manages DNS Sends email |
Guides
| Tool | What it does |
|---|---|
get_guide | Read 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.
Safety
Section titled “Safety”- 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.
Example prompts
Section titled “Example prompts”- “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.
Troubleshooting
Section titled “Troubleshooting”| 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. |
Data and privacy
Section titled “Data and privacy”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.