Provider REST API

20 actions

Connect Claude to MailerLite

Manage subscribers, groups and segments, and draft, schedule and report on email campaigns. Toolspoke puts 20 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API token
Actions exposed: 20
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install MailerLite
Open the marketplace in your workspace, add MailerLite to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api token. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. MailerLite shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What MailerLite asks for

API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API tokenRequired: MailerLite → Integrations → MailerLite API → Use → Generate new token. The token is shown once, and it reaches the whole account it was created in.; eyJ0eXAiOiJKV1Qi…

What Claude can do in MailerLite

20 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 12Reads
Writes: 5Writes
Destructive: 3Destructive

Reads

Fetches data and changes nothing.

list_subscribers
List subscribers, optionally narrowed to one status. Paged by cursor - pass the cursor from the previous response's meta to get the next page.
get_subscriber
Read one subscriber, with their fields, status and groups. Takes either the subscriber id or the email address.
get_subscriber_activity
Read one subscriber's activity log - sends, opens, clicks, bounces, unsubscribes - newest first.
list_groups
List subscriber groups with their counts and open and click rates. Takes no required arguments and reads real account data, which is why an install tests itself with it.
list_group_subscribers
List the subscribers in one group. Defaults to active subscribers; paged by cursor.
list_segments
List the segments on this account (at most 250 exist per account).
list_segment_subscribers
List the subscribers that match one segment. Defaults to active subscribers; paged by cursor.
list_campaigns
List campaigns by status (default ready) and type.
get_campaign
Read one campaign - its settings, recipients, schedule and, once sent, its open and click stats.
get_campaign_subscriber_activity
Per-subscriber results for a sent campaign - who opened, clicked, bounced or unsubscribed.
list_forms
List signup forms of one type with their conversion stats.
list_form_subscribers
List the subscribers who signed up through one form. Defaults to active subscribers; paged by cursor.

Writes

Creates or updates something on the other side.

upsert_subscriber
Add a subscriber, or update the one that already has this email. A write rather than destructive: it sends nothing by itself, though it decides who later campaigns reach, so consent is the caller's responsibility. Groups listed here are added; groups not listed are left as they are.
create_group
Create a subscriber group.
assign_subscriber_to_group
Add an existing subscriber to a group. unassign_subscriber_from_group undoes it.
unassign_subscriber_from_group
Remove a subscriber from one group. The subscriber stays on the account and can be assigned again.
create_campaign
Create a draft regular campaign with one email. A write, not destructive: a draft reaches nobody until schedule_campaign is called. The from address must be verified in MailerLite. HTML content is accepted only on plans that allow custom HTML; otherwise design the email in the MailerLite editor before scheduling. Send groups or segments; if both are sent, MailerLite uses only the segments.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

delete_subscriber
Remove a subscriber from the account. They stop receiving everything at once; MailerLite keeps the record so a later re-signup restores it, but nothing here can undo the removal.
schedule_campaign
Send a campaign now or schedule it. Destructive: it delivers email to real subscribers, and once delivery starts it cannot be recalled. delivery=instant sends immediately; scheduled needs date, hours and minutes; timezone_based needs hours and minutes; smart_sending needs date. cancel_campaign stops a scheduled one before it goes out.
cancel_campaign
Cancel a scheduled (ready) campaign and return it to draft. Classified destructive because it overrides a send someone else may have set up; it fails with 400 when the campaign is not in the ready state.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 20 actions above are the whole of it. A call to any other name is refused before it reaches MailerLite rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to MailerLite of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from MailerLite: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in MailerLite. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around MailerLite's own rate limits. A call that MailerLite refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in MailerLite?

20 named actions: 12 that only read, 5 that write and 3 that delete or permanently alter something. They include list_subscribers, get_subscriber and get_subscriber_activity. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the MailerLite connector need?

API token. The connector asks for api token. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the MailerLite connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 20 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the MailerLite connector not do?

The 20 actions above are the whole of it. A call to any other name is refused before it reaches MailerLite rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to MailerLite of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in MailerLite. An agent has to ask. Toolspoke does not retry, queue or back off around MailerLite's own rate limits. A call that MailerLite refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches MailerLite's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls MailerLite?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More marketing connectors

Browse all of them