Oksign
Sign online contracts, purchase orders, forms, you name it. Simple and legal.
Verdict
Common use cases
- Verify contract status during deal calls
- List pending signatures before weekly review
- Remove outdated documents from shared briefcases
- Check credit balance before bulk sends
- Open editor to add signature fields
Integration
- Vendor
- Oksign
- Category
- other
- Auth
- API_KEY
- Tools
- 17
- Composio slug
oksign
Tools
- Check Document Exists
Tool to check if a signed or unsigned document still exists on the OKSign platform. Use when you need to verify document availability before performing operations.
- Create Editor Express Session
Tool to invoke the OKSign Editor Express for modifying documents and form descriptors. Use when you need to open documents in an interactive editor where users can add signature fields, form fields, and configure signing workflows. The edit
- Get Active Documents
Tool to retrieve all active document IDs and properties from OKsign account. Use when you need to list documents visible in the Active Documents tab. Note: Rate limited to 1 request per 3 minutes.
- Remove Briefcasedestructive
Tool to remove a previously created briefcase from OKSign platform. Use when you need to delete a briefcase that is no longer needed. The briefcase is identified by the token received when it was created.
- Remove Contactsdestructive
Tool to remove specified contacts from the account's contact list. Use when you need to delete one or more contacts by providing their name and email.
- Remove Documentdestructive
Tool to remove a signed or unsigned document from the OKSign platform. Use when you need to delete a document and its signed copies from storage. Note: If document is removed immediately after signing while platform processes notifications,
- Remove SignExpress Tokendestructive
Tool to remove a previously uploaded SignExpress tokeninfo JSONObject from the OKSign platform. Use when you need to clean up or invalidate a SignExpress token that was created for sign button integration.
- Retrieve Account Credits
Tool to retrieve account credit balance and storage information. Use when you need to check available credits or storage capacity.
- Retrieve Briefcase Information
Tool to retrieve a previously uploaded briefcase tokeninfo for consultation. Use when you need to examine bundled document properties and signer requirements without re-creating the briefcase.
- Retrieve Contacts
Tool to retrieve the list of contacts stored in the account. Use when you need to access all contacts with their details including name, email, mobile number, and role.
- Retrieve Linked Document List
Tool to retrieve the list of linked signed or source document IDs related to a specific document. Use when you need to find linked documents (either the signed version of a source document, or the source of a signed document).
- Retrieve Users
Tool to retrieve the list of users associated with the OkSign account. Use when you need to get all users in an account.
- Update Organization Token Info
Tool to update organizational token information and settings for the account. Use when you need to configure or modify callback URL, webhook URL, or return URL for the organization's token.
- Upload Contacts
Tool to insert or update contact information in the account's contact list. Use when you need to add new contacts or update existing ones with details like name, email, phone, mobile, address, company, or identifier.
- Upload Document
Tool to upload a PDF or Word document to OKSign platform for completion and/or signing. Use when you need to add a new document that requires signatures. Maximum file size is 10 MB. Supported formats: PDF, DOC, DOCX.
- Upload Form Descriptor
Tool to upload form descriptor defining signature fields and other field types to a document. Use when you need to add form fields, signature areas, and configure signing workflows for a document.
- Upload Notifications
Tool to upload notifications defining email(s) and/or SMS(es) to be sent to signer(s) with signing links. Use when you need to send notification emails or SMS messages to document signers.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and select Oksign from the list. 2. Log into your Oksign account, navigate to API Settings, and generate a new API key. 3. Copy the key and paste it into the Switchy connection dialog, then click Connect. 4. Switchy confirms the connection by retrieving your account credit balance. 5. Open any Space and type '@Oksign retrieve account credits' to verify the integration works. 6. To check active documents, type '@Oksign get active documents' — note this command is rate-limited to once every three minutes. 7. Use '@Oksign check document exists' followed by a document ID to confirm a file is still on the platform before performing other operations.
What teammates see: by default, memories from Oksign are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Documents
@Oksign get active documents so I can see which contracts are still pending signatures.Open in a Space →
Check Document Status
@Oksign check if document ID 12345 exists and let me know if it's still available for signing.Open in a Space →
Remove Signed Document
@Oksign remove document ID 67890 now that the signed copy is saved in our records system.Open in a Space →
Verify Account Credits
@Oksign retrieve my account credits and storage balance so I can plan this week's contract sends.Open in a Space →
Open Document Editor
@Oksign create an editor express session for the NDA template so I can add signature boxes and date fields.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Oksign show me all active documents in my account and their current status
Here are your active documents: 1. **Q4_Sales_Agreement.pdf** – Awaiting signature from 2 recipients (sent Dec 15) 2. **NDA_Acme_Corp.pdf** – Fully signed (completed Dec 12) 3. **Contractor_Agreement_Smith.pdf** – Draft, not yet sent 4. **Partnership_MOU.pdf** – Awaiting signature from 1 recipient (sent Dec 10) This represents documents currently visible in your Active Documents tab. Note that this is an illustrative example; your actual document list will vary based on your account activity.
This example uses the Get Active Documents tool, which is rate-limited to one request every 3 minutes. Useful for getting a snapshot of pending and completed signature workflows. Requires API key authentication with read access to your Oksign account.
@Oksign remove the old NDA document from last quarter and delete the contact for John Doe at example.com
I've completed both actions: **Document Removal:** Successfully removed "Q3_NDA_Template.pdf" and all associated signed copies from your Oksign storage. **Contact Removal:** Deleted contact "John Doe" (john.doe@example.com) from your account contact list. Both items are permanently removed from the platform. This is an illustrative example showing how the MCP handles cleanup operations.
Demonstrates the Remove Document and Remove Contacts tools for account maintenance. These are destructive operations with no undo—documents and contacts are permanently deleted. If a document was just signed, wait a few moments before removal to ensure processing completes.
@Oksign check my account credits and tell me if I have enough capacity to send 50 documents this month
**Account Status:** - Available Credits: 1,247 - Storage Used: 3.2 GB of 10 GB (32%) **Capacity Analysis:** With 1,247 credits remaining, you have sufficient capacity to send 50 documents this month. Each document typically consumes 1-2 credits depending on recipient count and features used. At current usage, you'd consume approximately 75-100 credits for 50 documents, leaving a comfortable buffer. This is an illustrative example of credit analysis.
Uses the Retrieve Account Credits tool to provide visibility into your Oksign resource limits. Helpful for planning bulk signature campaigns or assessing whether you need to purchase additional credits before a deadline. Credit consumption varies by document complexity and recipient count.
Use-case deep-dives
When Oksign's removal tools matter for post-deal document hygiene
A 6-person finance team just closed an acquisition and needs to purge 400+ NDAs, term sheets, and draft agreements from their signing platform before onboarding the acquired company's contracts. Oksign's batch removal tools (Remove Document, Remove Briefcase, Remove Contacts) let them script the cleanup without clicking through a web UI. The Check Document Exists tool prevents errors when a document was already archived by legal. This scenario works if your team has API access and someone who can write a 20-line Python loop. If you're doing this once a year and have under 50 documents, the manual UI is faster. Use Oksign's MCP when document volume makes scripting worth the setup cost.
Tracking signature spend when your contract velocity is high
A 3-person ops team at a B2B SaaS company sends 80-120 customer agreements per week and needs to forecast their Oksign credit burn for budget planning. The Retrieve Account Credits tool surfaces balance and storage in real time, so they can pipe it into a Slack alert when credits drop below a threshold. This beats logging into the Oksign dashboard every Monday. The rate limit on Get Active Documents (1 request per 3 minutes) means you can't poll aggressively, but for a weekly finance check-in, it's fine. If your contract volume is under 20 per month, manual checks are simpler. Use this MCP when signature spend is a line item your CFO watches.
When support needs to verify document state without escalating to legal
A 5-person customer success team fields 10-15 tickets per week asking "did my contract go through?" before the customer checks their email. The Check Document Exists tool lets a support agent verify the document is still on the platform and hasn't been removed, without pinging legal or digging through the Oksign admin panel. This works if your support team uses a shared AI workspace where they can invoke the MCP in a thread with the customer's email or document ID. If your support volume is under 5 tickets per month, a shared login to the Oksign dashboard is easier. Use this MCP when support handles signature status questions daily and needs to deflect legal escalations.
Frequently asked
What does the Oksign MCP let me do in Switchy?
It lets you manage e-signature workflows without leaving your AI workspace. You can check if documents exist, retrieve active documents, remove old files, and open the Oksign Editor Express to add signature fields. You can also manage contacts, briefcases, and SignExpress tokens. It's useful when you need to automate document prep or audit what's in your Oksign account.
Do I need admin access to connect Oksign via API key?
You need an Oksign account with an active API key. Oksign doesn't publish granular permission tiers in their docs, so assume you need full account access to generate the key. If you're on a team plan, check with whoever manages your Oksign subscription before connecting it to Switchy.
Can the MCP send documents out for signature?
No. The MCP focuses on document management and editor access, not sending. You can check if documents exist, list active ones, and open the editor to add fields, but you can't trigger signature requests or track signer status. For that, use Oksign's web app or their dedicated sending API.
Why use this instead of just logging into Oksign?
Use the MCP when you want to script repetitive tasks or pull Oksign data into an AI conversation. For example, you can ask Switchy to list all active documents, check your credit balance, or remove a batch of old files without clicking through the Oksign UI. It's faster for bulk operations.
Who on the team should connect this MCP?
Whoever owns your Oksign account and has the API key. Since the MCP can remove documents and contacts, you don't want it connected by someone who shouldn't have delete permissions. If multiple people need access, consider creating a dedicated Oksign service account with its own key.