Provider REST API

14 actions

Connect Claude to Docusign

Track envelopes and signers, read templates and audit trails, and prepare, send or void envelopes for signature. Toolspoke puts 14 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: Sign in with Docusign
Actions exposed: 14
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

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

Sign in with Docusign. 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 base URIRequired: The Account Base URI from Docusign Admin → Settings → Apps and Keys, under My Account Information - for example https://na3.docusign.net. Paste it without /restapi. It differs per account (each account lives on one data centre), so there is no default; get_user_info also returns it as base_uri.; https://na3.docusign.net
API account IDRequired: The API Account ID (a GUID, not the short account number) from Docusign Admin → Settings → Apps and Keys, under My Account Information. Every path in this connector is built from it.; 1a2b3c4d-…

What Claude can do in Docusign

14 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: 9Reads
Writes: 2Writes
Destructive: 3Destructive

Reads

Fetches data and changes nothing.

get_user_info
The signed-in user's name and email, and every Docusign account they belong to with its account_id and base_uri. Use it to find the two values the other actions need, or to check which account is the default.
get_account
Read the account itself - its name, plan, billing period and envelope allowance.
list_envelopes
Search envelopes whose status changed since a date, newest activity first by default. Docusign requires from_date unless envelope_ids is given, and returns at most 1000 per call; follow start_position for more. Returns subjects, senders and status, not document content.
get_envelope
Read one envelope's status, subject, sender, timestamps and expiry. Add include=recipients,documents,tabs to get those in the same call.
list_recipients
List an envelope's recipients with each one's routing order and status - sent, delivered, signed, declined, with timestamps and any decline reason. include_tabs adds the values each signer entered, which is form data.
list_envelope_documents
List the documents in an envelope - document ID, name, page count, order and type, including the certificate of completion (documentId certificate). Returns metadata only; the file bytes are not fetched.
list_audit_events
The envelope's audit trail: every event - created, sent, viewed, signed, voided - with who, when and from which IP address. The same history as the certificate of completion.
list_templates
List the templates this user can use, with name, description, owner, folder and last-used date. The connection test, because it reads real account data under the signature scope.
get_template
Read one template - its documents, recipient roles (the roleName values create_draft_from_template fills) and default email subject and message.

Writes

Creates or updates something on the other side.

create_draft_envelope
Create a draft envelope from documents you supply. It is always saved as a draft (status created) - nobody is emailed until send_envelope. Returns the envelopeId. Place signature fields with tabs on each signer, e.g. anchor tabs that find a string in the document.
create_draft_from_template
Create a draft envelope from a template, filling its roles with real people. It is always saved as a draft (status created) - nobody is emailed until send_envelope. Returns the envelopeId.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

send_envelope
Send a draft envelope for signature. Classified destructive: Docusign emails the first signers at once, the envelope counts against the account's allowance, and the only way back is to void it, which the signers also see.
send_reminder
Email the envelope again to every recipient who has not yet acted. Classified destructive because it sends mail to people outside the workspace.
void_envelope
Void a sent envelope that is not yet complete, so nobody can sign it. Irreversible: every recipient is emailed the reason, and a voided envelope cannot be reopened - a new one has to be sent.

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

Before you connect it

What can Claude do in Docusign?

14 named actions: 9 that only read, 2 that write and 3 that delete or permanently alter something. They include get_user_info, get_account and list_envelopes. 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 Docusign connector need?

Sign in with Docusign. The connector asks for account base uri and api account id. 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 Docusign connector work with Cursor and Codex, or only Claude?

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

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

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 productivity connectors

Browse all of them