Read documents, signatures, contacts and credits; manage contacts and remove documents. For teams managing electronic signatures and documents with OKSign. 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": {
"oksign": {
"url": "https://oksign.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"oksign": {
"type": "http",
"url": "https://oksign.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 active documents and inspect their form descriptors to review required signature fields and the current signature counts.
oksign_list_active_documents oksign_get_form_descriptor
List documents signed within a time window and inspect a signed document’s metadata, including its signature counts and completed field values.
oksign_list_signed_documents oksign_get_document_metadata
Review the contact list and add or update named contacts when requested. The update preserves the rest of the contact list.
Changes data · oksign_list_contacts oksign_upsert_contacts
Inspect email or SMS delivery problems for a time window and check the account’s remaining credits and storage.
oksign_list_notification_errors oksign_get_credits
The login page asks for your API header value (x-oksign-authorization).
Find it in your OKsign account under REST API → API Console: it is the value of the x-oksign-authorization header, three parts joined by semicolons, e.g. 100693;463204-5BC1F362-…;marketing (add an organizational token there first if you have none). The credentials are used only to call the OKsign API on your behalf; they are 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 API header value (x-oksign-authorization). 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 OKSign connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
oksign_get_credits | read | Get credits and storage The account's remaining credits (quantity), when they expire (validuntil), the plan (subscription), whether it is paid, and storage used (account_size) versus the maximum (max_account_size) in bytes. GET /v1/credits/retrieve. |
oksign_list_users | read | List users The users of the OKsign account: name, email, mobile, role, status, language and the immutable signerid (use it to tell who signed). GET /v1/users/retrieve. |
oksign_list_email_templates | read | List email templates The email templates defined in the account: id, name, subject, HTML body, reminder_days and repeat. GET /v1/email-templates/retrieve. |
oksign_list_contacts | read | List contacts The account's contact list: name, email, mobile, actingas (capacity) and group. GET /v1/contacts/retrieve. |
oksign_list_active_documents | read | List active documents Documents in the account's Active Documents tab: docid, filename, creator, createdate, signatures required/valid, orgtoken, status (1 active, 10 briefcase, 11 document in a briefcase, 12 reusable, 14 template), viaapi and signed_docid when signed. OKsign allows this call only once every 3 minutes (429 otherwise). GET /v1/documents/active. |
oksign_list_signed_documents | read | List signed documents Documents uploaded through the API that were signed between two moments: signed_docid, source_docid, filename, signerid, signing source, signature counts, completed fields, credits per signer and timestamp. Keep the window short; OKsign allows this call only once every 3 minutes (429 otherwise). GET /v1/documents/signed. |
oksign_list_notification_errors | read | List email and SMS delivery errors Email and SMS delivery problems (hard_bounce, soft_bounce, blocked, spam, invalid_email, deferred) for signing invitations sent between two moments: recipient, source_docid, reason, orgtoken and timestamp. Only error events are reported. OKsign allows this call only once every 3 minutes (429 otherwise). GET /v1/webhooks/retrieve. |
oksign_document_exists | read | Check a document exists Whether a (signed) document still exists on the platform; returns its filename and whether it is a template. GET /v1/document/exists. |
oksign_get_document_metadata | read | Get signed document metadata Metadata of a signed document (pass the signed_docid): filename, size, signatures required/valid, who signed, and the values of all completed fields (can contain personal data). Metadata v2. GET /v2/metadata/retrieve. |
oksign_get_form_descriptor | read | Get a document's form descriptor The form descriptor of an uploaded document: its signature and form fields (type, page, position, signer, required, signing options) and the signing URL of each signer. The URLs let their holders sign, so share them only with the signer. GET /v1/formdesc/retrieve. |
oksign_get_linked_document | read | Find the source or signed copy of a document Given a source_docid, the signed_docid of its signed copy (absent if not signed yet) and the timestamp; given a signed_docid, the source_docid. An empty result means the document never existed here or was removed. GET /v1/linkedlist/retrieve. |
oksign_upsert_contacts | write | Add or update contacts WRITE: add contacts to the account's contact list, or update them when a contact with the same email AND name exists (its other fields are replaced). Existing contacts are never cleared. Contacts OKsign rejects are skipped and reported. POST /v1/contacts/upload. |
oksign_remove_contacts | write | Remove contacts WRITE: permanently remove contacts from the account's contact list. A contact is identified by its email AND name. Cannot be undone (re-add with oksign_upsert_contacts). POST /v1/contacts/remove. |
oksign_remove_document | write | Remove a document WRITE: permanently remove a (signed) document from the OKsign platform. This deletes the file and its pending webhook events and cannot be undone. A signed document removed right after its callback may answer 'Too soon': retry later. DELETE /v1/document/remove. |
oksign_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. | |
oksign_request_feature | Request a missing feature Tell usefulapi that the user needs something the OKSign 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. | |
oksign_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on OKSign (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. | |
oksign_cancel_subscription | Cancel the Pro subscription Cancel the caller's OKSign 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 oksign_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 connected account | $9/mo · $90/yr | 10,000 tool calls / month |
Pro covers this OKSign server only. Subscribe with oksign_upgrade (it returns a Stripe Checkout link). Cancel any time with oksign_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running oksign_upgrade before then undoes the cancel. Or write to [email protected].
Review documents awaiting signatures. Review recently signed documents. Add or update signing contacts. Review delivery errors and account credits. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by OKSign. The server calls the OKSign API with your own OKSign 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 API header value (x-oksign-authorization). 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 API header value (x-oksign-authorization). 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 OKSign 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 OKSign.
Yes, if you approve it. 3 of the 14 OKSign 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 10,000 tool calls / month tool calls, for this OKSign server only. Cancel any time: Pro then runs to the end of the paid period. Run oksign_usage_status to see how many calls you used.
Ask the AI to run oksign_upgrade: it returns a Stripe Checkout link. To cancel, run oksign_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 oksign_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.