Read sign requests and signers; send, remind, extend and cancel sign requests in Stiply. For teams that send documents for e-signing with Stiply. 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": {
"stiply": {
"url": "https://stiply.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"stiply": {
"type": "http",
"url": "https://stiply.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 sign requests and filter by status, such as published or rejected. Open one to read its message, dates and reject reason.
stiply_list_sign_requests stiply_get_sign_request
Open a sign request and list its signers with their role. Read the progress trail to see who opened the mail and who signed.
stiply_list_signers stiply_get_sign_request_progress
Look up a sign request with the external key that your system stored. Then list the documents attached to it.
stiply_get_sign_request_by_external_key stiply_list_documents
Find the open sign request. Send a reminder by email to the signers who have not signed. Extend the term if the date is close.
Changes data · stiply_list_sign_requests stiply_send_reminder stiply_extend_term
Create a sign request from PDF links and send it to the signers. Confirm the signers first, because Stiply emails them at once.
Changes data · stiply_create_sign_request
The login page asks for your Stiply Personal Access Token.
Create it in Stiply → Settings → API (app.stiply.nl/settings/api). Your 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 Stiply Personal Access 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 Stiply connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
stiply_list_sign_requests | read | List sign requests List sign requests (documents sent for e-signing) with status, title, sent/expiry/signed timestamps. Filter by status (draft, published, all_signed, completed, rejected, canceled, expired, ...). Stiply API: GET /v2/sign_requests. |
stiply_get_sign_request | read | Get a sign request Get one sign request by id: status, timestamps, message, reject reason, owner. Stiply API: GET /v2/sign_requests/{id}. |
stiply_get_sign_request_by_external_key | read | Get a sign request by external key Find a sign request by the external_key set when it was created. Stiply API: GET /v2/sign_requests/by_key/{external_key}. |
stiply_get_sign_request_progress | read | Get sign request progress Get the audit trail of a sign request: each action (sent, opened, signed, ...) with time, IP, location and email status. Stiply API: GET /v2/sign_requests/{id}/progress. |
stiply_list_signers | read | List signers List the signers of a sign request with email, name, role (signer/approver/cc/dc), authentication method and sign URL. Stiply API: GET /v2/sign_requests/{id}/signers. |
stiply_list_documents | read | List documents of a sign request List the documents attached to a sign request (metadata only, no file download). Stiply API: GET /v2/sign_requests/{id}/documents. |
stiply_create_sign_request | write | Create and send a sign request WRITE: create a sign request and SEND it. Stiply downloads each PDF from file_urls and emails the signers at once, so confirm the signers with the user first. Stiply API: POST /v2/sign_requests. |
stiply_send_reminder | write | Send a reminder WRITE: email a reminder to the signers who have not signed yet. Stiply API: POST /v2/sign_requests/{id}/actions/send_reminder. |
stiply_extend_term | write | Extend the term WRITE: extend the signing term of a sign request. Stiply API: POST /v2/sign_requests/{id}/actions/extend_term. |
stiply_cancel_sign_request | write | Cancel a sign request WRITE: cancel a sign request. This cannot be undone. Stiply API: POST /v2/sign_requests/{id}/actions/cancel. |
stiply_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. | |
stiply_request_feature | Request a missing feature Tell usefulapi that the user needs something the Stiply 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. | |
stiply_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Stiply (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. | |
stiply_cancel_subscription | Cancel the Pro subscription Cancel the caller's Stiply 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 stiply_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 Stiply server only. Subscribe with stiply_upgrade (it returns a Stripe Checkout link). Cancel any time with stiply_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running stiply_upgrade before then undoes the cancel. Or write to [email protected].
See which documents still wait for a signature. Check who has not signed yet. Find a sign request by the key of your own system. Remind the signers of an open request. Send a new document for signature. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Stiply. The server calls the Stiply API with your own Stiply 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 Stiply Personal Access 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 Stiply Personal Access 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 Stiply 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 Stiply.
Yes, if you approve it. 4 of the 10 Stiply tools can create or change data. The other 6 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 Stiply server only. Cancel any time: Pro then runs to the end of the paid period. Run stiply_usage_status to see how many calls you used.
Ask the AI to run stiply_upgrade: it returns a Stripe Checkout link. To cancel, run stiply_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 stiply_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.