Read documents, signatures, contacts and credits; manage contacts and remove documents. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the OKSign connector, then ask in plain words. The AI picks the tools.
For teams managing electronic signatures and documents with OKSign.
List active documents and inspect their form descriptors to review required signature fields and the current signature counts.
List documents signed within a time window and inspect a signed document’s metadata, including its signature counts and completed field values.
Review the contact list and add or update named contacts when requested. The update preserves the rest of the contact list.
Changes dataInspect email or SMS delivery problems for a time window and check the account’s remaining credits and storage.
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.
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": {
"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"
}
}
} 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 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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper connected account | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per connected account | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this OKSign server only. Ask your AI to run oksign_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with oksign_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with oksign_upgrade before then undoes the cancel. Or write to [email protected].
oksign_get_creditsoksign_list_usersoksign_list_email_templatesoksign_list_contactsoksign_list_active_documentsoksign_list_signed_documentsoksign_list_notification_errorsoksign_document_existsoksign_get_document_metadataoksign_get_form_descriptoroksign_get_linked_documentoksign_upsert_contactsoksign_remove_contactsoksign_remove_documentoksign_usage_statusoksign_request_featureoksign_upgradeoksign_cancel_subscriptionReview 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. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this OKSign server only. Cancel any time: your paid plan 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 and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run oksign_cancel_subscription. Your paid plan 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.