Provider REST API

9 actions

Connect Claude to Twilio

Send SMS, read message and call logs, and look up phone numbers. Toolspoke puts 9 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: Account SID and auth token
Actions exposed: 9
Cost per call (typical): 1 credit
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Twilio
Open the marketplace in your workspace, add Twilio to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with account sid and auth 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. Twilio 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 Twilio asks for

Account SID and auth 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.

Account SIDRequired: The 34-character Account SID starting with AC, from Console → Account Info. Every account-scoped path in this connector is built from it, which is why it is asked for separately from the token below.; AC…
Account SID and auth tokenRequired: Paste the Account SID, a colon, then the auth token - both from Console → Account Info. Twilio reads HTTP Basic with the SID as the username and the auth token as the password, so this one field is what gets base64-encoded into the Authorization header. A subaccount works too: use that subaccount's own SID in both fields.; AC…:your_auth_token

What Claude can do in Twilio

9 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: 8Reads
Writes: 0Writes
Destructive: 1Destructive

Reads

Fetches data and changes nothing.

list_messages
List messages sent and received on this account, newest first. Filter by the number at either end, or by the date sent. Twilio's date filters are inclusive on both sides.
get_message
Retrieve one message by SID, with its body, status, error code, direction, segment count and price.
list_calls
List voice calls on this account, newest first. Filter by the number at either end, by call status, or by when the call started. Returns call metadata - who called whom, for how long, at what price - and never recording audio.
get_call
Retrieve one call by SID: its status, direction, duration, price, and the numbers at both ends.
list_phone_numbers
List the phone numbers this account owns, with their capabilities and the webhooks configured on each. Call it before send_sms to find a number you can legitimately send from.
get_account_balance
Return the account's remaining Twilio balance and its currency. Takes no arguments, reads nobody's messages and costs nothing, which is why it is what an install tests itself with.
lookup_phone_number
Look up a phone number through the Lookup v2 API: whether it is valid, its country, and - when you ask for them - its line type, carrier, or the name it is registered to. Data packages beyond the free validation are billed per lookup, so ask only for the ones you need. This is the one action on a different host: Lookup lives at lookups.twilio.com, not api.twilio.com.
list_usage_records
List usage and spend on this account, one record per billing category. Use it to answer what a month of messaging cost. Category is a Twilio usage category name such as sms, calls or lookups; leave it out for every category.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

send_sms
Send an SMS or MMS from a Twilio number. This is classified destructive rather than write, and deliberately so: it delivers a message to a real handset, it cannot be recalled once sent, and Twilio bills per segment. A write grant can read every log in this connector and send nothing. Supply either from (a Twilio number you own, in E.164) or messaging_service_sid (a Messaging Service that picks the number for you) - Twilio rejects the request if neither is present.

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 9 actions above are the whole of it. A call to any other name is refused before it reaches Twilio 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 Twilio 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 Twilio: 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 Twilio. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Twilio's own rate limits. A call that Twilio refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Twilio?

9 named actions: 8 that only read and 1 that delete or permanently alter something. They include send_sms, list_messages and get_message. 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 Twilio connector need?

Account SID and auth token. The connector asks for account sid and account sid and auth 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 Twilio connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 9 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 Twilio connector not do?

The 9 actions above are the whole of it. A call to any other name is refused before it reaches Twilio 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 Twilio 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 Twilio. An agent has to ask. Toolspoke does not retry, queue or back off around Twilio's own rate limits. A call that Twilio 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 Twilio'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 Twilio?

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 the credits spent. 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 communication connectors

Browse all of them