Read documents, signature requests and templates; send, cancel and resend requests in SignRequest. For teams that collect e-signatures with SignRequest. Hosted by usefulapi — connect from Claude, ChatGPT, 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": {
"signrequest": {
"url": "https://signrequest.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"signrequest": {
"type": "http",
"url": "https://signrequest.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
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.
List the signature requests and open one to see the status of each signer.
signrequest_list_signrequests signrequest_get_signrequest
Search the documents and read one document with its status.
signrequest_search_documents signrequest_get_document signrequest_list_events
Send a document or a template to the signers by email.
Changes data · signrequest_list_templates signrequest_send_document
Resend the signature request email to the signers who did not sign yet.
Changes data · signrequest_get_signrequest signrequest_resend_signrequest_email
Cancel a signature request that went to the wrong person.
Changes data · signrequest_get_signrequest signrequest_cancel_signrequest
The login page asks for your SignRequest team API token.
Create it in SignRequest → Team settings → API (the team API settings page). The token is used only to call the API on your behalf and to derive a private account id; 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 SignRequest team API 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.
Turn on the SignRequest connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
signrequest_list_documents | read | List documents List documents of the team with status, signers state and signing log links. API: GET /documents/. |
signrequest_get_document | read | Get a document Get one document by uuid: status, signrequest with all signers, signing log, attachments, and temporary download links (pdf). API: GET /documents/{uuid}/. |
signrequest_search_documents | read | Search documents Search documents by free text, name, signer email or status. API: GET /documents-search/. |
signrequest_list_signrequests | read | List signature requests List signature requests (the sent requests with their signers). API: GET /signrequests/. |
signrequest_get_signrequest | read | Get a signature request Get one signature request by uuid, with each signer's viewed, signed, declined and forwarded state. API: GET /signrequests/{uuid}/. |
signrequest_list_templates | read | List templates List document templates (use a template uuid with signrequest_send_document). API: GET /templates/. |
signrequest_get_template | read | Get a template Get one template by uuid, with its signer placeholders. API: GET /templates/{uuid}/. |
signrequest_list_teams | read | List teams List the teams the token can see (name, subdomain, sandbox flag). API: GET /teams/. |
signrequest_get_team | read | Get a team Get one team by subdomain. API: GET /teams/{subdomain}/. |
signrequest_list_team_members | read | List team members List team members with admin, owner and active flags. API: GET /team-members/. |
signrequest_list_events | read | List events List document events (sent, viewed, signed, declined, cancelled, bounced) and their callback delivery state. API: GET /events/. |
signrequest_send_document | write | Send a document for signature WRITE: creates a document and e-mails a signature request to the signers right away (not undoable except with signrequest_cancel_signrequest). Give exactly one source: a template uuid, a public file_from_url, or base64 file_from_content with file_from_content_name. API: POST /signrequest-quick-create/. |
signrequest_cancel_signrequest | write | Cancel a signature request WRITE: cancels a signature request that is not fully signed or declined. Signers who have not signed can no longer open the document. Not undoable. API: POST /signrequests/{uuid}/cancel_signrequest/. |
signrequest_resend_signrequest_email | write | Resend signature request e-mail WRITE: sends the signature request e-mail again as a reminder to every signer who did not sign yet but already got the e-mail. API: POST /signrequests/{uuid}/resend_signrequest_email/. |
signrequest_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
signrequest_request_feature | Request a missing feature Tell usefulapi that the user needs something the SignRequest 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. | |
signrequest_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on SignRequest (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
signrequest_cancel_subscription | Cancel the Pro subscription Cancel the caller's SignRequest Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run signrequest_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| 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 SignRequest server only. Subscribe with signrequest_upgrade (it returns a Stripe Checkout link). Cancel any time with signrequest_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running signrequest_upgrade before then undoes the cancel. Or write to [email protected].
Check who has not signed. Find a document. Send a document for signature. Remind signers who have not signed. Cancel a request that is wrong. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by SignRequest. The server calls the SignRequest API with your own SignRequest 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 SignRequest team API 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 SignRequest team API 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 SignRequest 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 SignRequest.
Yes, if you approve it. 3 of the 14 SignRequest tools can create or change data. The other 11 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 SignRequest server only. Cancel any time: Pro then runs to the end of the paid period. Run signrequest_usage_status to see how many calls you used.
Ask the AI to run signrequest_upgrade: it returns a Stripe Checkout link. To cancel, run signrequest_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 signrequest_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.