Create, send and track e-signature documents with their files and recipients in CloudSign. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the CloudSign connector, then ask in plain words. The AI picks the tools.
For teams that send contracts and documents for e-signature with CloudSign.
List the team's documents by status, then open one to see its files and participants. Status 1 means it waits for recipients.
List the documents with status 2, concluded, and open one to read its files and participants.
Create a draft, upload the PDF, add the recipient, then send it. Recipients get an email at once, and sending cannot be undone.
Changes dataOpen the document to check its status. Then send it again, which emails the recipients a reminder.
Changes dataOpen the draft to check it, then delete it. Sent documents cannot be deleted.
Changes dataThe login page asks for your CloudSign Web API client ID.
Your team admin enables the Web API and issues the client ID in CloudSign's Web API settings. It is 36 characters: letters, digits and hyphens. The client ID is used only to call the CloudSign API for you and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"cloudsign": {
"url": "https://cloudsign.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"cloudsign": {
"type": "http",
"url": "https://cloudsign.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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 CloudSign Web API client ID. 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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this CloudSign server only. Subscribe with cloudsign_upgrade (it returns a Stripe Checkout link). Cancel any time with cloudsign_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running cloudsign_upgrade before then undoes the cancel. Or write to [email protected].
cloudsign_list_documentscloudsign_get_documentcloudsign_list_cabinetscloudsign_create_documentcloudsign_update_documentcloudsign_add_participantcloudsign_add_filecloudsign_send_documentcloudsign_delete_draftcloudsign_usage_statuscloudsign_request_featurecloudsign_upgradecloudsign_cancel_subscriptionCheck which documents still wait for signature. Review the concluded documents. Create a draft and send it for signature. Send a reminder for an unsigned document. Delete a draft that is no longer needed. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by CloudSign. The server calls the CloudSign API with your own CloudSign access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your CloudSign Web API client ID. 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 CloudSign Web API client ID. 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 CloudSign 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 CloudSign.
Yes, if you approve it. 6 of the 9 CloudSign tools can create or change data. The other 3 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this CloudSign server only. Cancel any time: Pro then runs to the end of the paid period. Run cloudsign_usage_status to see how many calls you used.
Ask the AI to run cloudsign_upgrade: it returns a Stripe Checkout link. To cancel, run cloudsign_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 cloudsign_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, ChatGPT, Codex, 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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.