Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"sendlane": {
"url": "https://sendlane.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"sendlane": {
"type": "http",
"url": "https://sendlane.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Sendlane API v2 token.
In Sendlane open the API section, choose Generate a v2 access token and copy it (it is shown once). Your token is used only to call the Sendlane API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Sendlane API v2 token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
sendlane_list_lists | read | List lists List the audience lists of the account: id, name, description, status, created date. GET /lists. |
sendlane_get_list | read | Get list One audience list by id. GET /lists/{listId}. |
sendlane_list_list_contacts | read | List contacts of a list Contacts on one list: email, name, phone, subscribed/suppressed state, tags, custom fields, lifetime value. GET /lists/{listId}/contacts. |
sendlane_list_list_unsubscribed | read | List unsubscribed contacts of a list Contacts that unsubscribed from one list. GET /lists/{listId}/unsubscribed. |
sendlane_list_contacts | read | List contacts All contacts of the account: email, name, phone, lists, tags, custom fields, subscribed/suppressed state. Filter by creation time with from/to. GET /contacts. |
sendlane_get_contact | read | Get contact One contact by id, with lists, tags, custom fields, consent, lifetime value and subscribed/suppressed state. GET /contacts/{contactId}. |
sendlane_list_unsubscribed_contacts | read | List unsubscribed contacts Contacts that unsubscribed from the account. GET /contacts/unsubscribed. |
sendlane_get_contact_subscriptions | read | Get contact subscriptions The list subscriptions of one contact: list, subscribed/suppressed state, who added it and when. GET /contacts/{contactId}/subscriptions. |
sendlane_get_contact_tags | read | Get contact tags The tags on one contact. GET /contacts/{contactId}/tags. |
sendlane_get_contact_custom_fields | read | Get contact custom fields The custom field values of one contact. GET /contacts/{contactId}/custom-fields. |
sendlane_list_tags | read | List tags The contact tags of the account: id, name, audience count. GET /tags. |
sendlane_get_tag | read | Get tag One tag by id. GET /tags/{tagId}. |
sendlane_list_tag_contacts | read | List contacts with a tag Contacts that carry one tag. GET /tags/{tagId}/contacts. |
sendlane_list_custom_fields | read | List custom fields The custom contact fields of the account: id, name, type. Use the ids when setting field values. GET /custom-fields. |
sendlane_list_segments | read | List segments The segments of the account: id, name, list, match rule, last count. GET /segments. |
sendlane_list_segment_contacts | read | List contacts of a segment Contacts in one segment: id, email, name, phone. GET /segments/{segmentId}/contacts. |
sendlane_list_campaigns | read | List campaigns Email campaigns: id, name, status, scheduled and sent time, automation. GET /campaigns. |
sendlane_get_campaign | read | Get campaign One email campaign by id. GET /campaigns/{campaignId}. |
sendlane_get_campaign_report | read | Get campaign report Statistics of one email campaign: sent, opens, clicks (unique too), bounced, suppressed, unsubscribed, spam, revenue. from/to limit the period. GET /campaigns/{campaignId}/report. |
sendlane_list_sms_messages | read | List SMS messages SMS messages (campaign and automation): id, name, campaign status, automation. GET /sms-messages. |
sendlane_get_sms_report | read | Get SMS report Statistics of one SMS message: sent, delivered, clicks, failed, replies, unsubscribed, credits, revenue. from/to limit the period. GET /sms-messages/{messageId}/report. |
sendlane_list_sender_profiles | read | List sender profiles The sender profiles (from name, from/reply email, postal address, default flag). GET /senders. |
sendlane_create_list | write | Create list WRITE: create an audience list. Not idempotent: calling it twice makes two lists. POST /lists. |
sendlane_update_list | write | Update list WRITE: rename a list and/or change its description (a full update: name is required, an omitted description may be cleared). PUT /lists/{listId}. |
sendlane_add_contacts_to_list | write | Add contacts to a list WRITE: add one or more contacts (up to 100) to a list; a contact that does not exist is created. Each needs an email or a phone. Sendlane accepts the request for processing (HTTP 202). Only add people who agreed to receive marketing. POST /lists/{listId}/contacts. |
sendlane_remove_contact_from_list | write | Remove a contact from a list WRITE: remove one contact from one list (the contact stays in the account). DELETE /lists/{listId}/contacts/{contactId}. |
sendlane_unsubscribe_contact | write | Unsubscribe a contact WRITE: unsubscribe one contact from email marketing. The contact stops receiving campaigns. POST /contacts/{contactId}/unsubscribe. |
sendlane_create_tag | write | Create tag WRITE: create a contact tag. POST /tags. |
sendlane_add_contact_tags | write | Tag a contact WRITE: put one or more existing tags on a contact. POST /contacts/{contactId}/tags. |
sendlane_remove_contact_tag | write | Untag a contact WRITE: remove one tag from a contact (the tag itself is kept). DELETE /contacts/{contactId}/tags/{tagId}. |
sendlane_set_contact_custom_fields | write | Set contact custom fields WRITE: add custom field values to a contact. Field ids come from sendlane_list_custom_fields. POST /contacts/{contactId}/custom-fields. |
sendlane_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
sendlane_request_feature | Request a missing feature Tell usefulapi that the user needs something the Sendlane tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
sendlane_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Sendlane tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
sendlane_cancel_subscription | Cancel the Pro subscription Cancel the caller's Sendlane Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run sendlane_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Sendlane server only. Subscribe with sendlane_upgrade (it returns a Stripe Checkout link). Cancel any time with sendlane_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sendlane_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Sendlane. The server calls the Sendlane API with your own Sendlane access, so it sees only the data that your account can see.
The login page asks for your Sendlane API v2 token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Sendlane API v2 token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Sendlane API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Sendlane.
Yes, if you approve it. 9 of the 31 Sendlane tools can create or change data. The other 22 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Sendlane server only. Run sendlane_usage_status to see how many calls you used.
Ask the AI to run sendlane_upgrade: it returns a Stripe Checkout link. To cancel, run sendlane_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with sendlane_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.