How to integrate Oksign MCP with Codex

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Oksign MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Oksign logoOksign
Api Key

Oksign is an online platform for signing contracts, purchase orders, and forms. It makes digital signatures fast, simple, and legally binding.

17 Tools

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Oksign MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Oksign with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Oksign MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Oksign MCP server, and what's possible with it?

The Oksign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Oksign account. It provides structured and secure access so your agent can perform Oksign operations on your behalf.

Conclusion

You've successfully integrated Oksign with Codex using Composio's MCP server. Now you can interact with Oksign directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Oksign operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Oksign operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities
TOOLS

Supported Tools

Every Oksign action and event your agent gets out of the box.

Remove Briefcase

Tool to remove a previously created briefcase from OKSign platform.

Retrieve Briefcase Information

Tool to retrieve a previously uploaded briefcase tokeninfo for consultation.

Remove Contacts

Tool to remove specified contacts from the account's contact list.

Retrieve Contacts

Tool to retrieve the list of contacts stored in the account.

Upload Contacts

Tool to insert or update contact information in the account's contact list.

Retrieve Account Credits

Tool to retrieve account credit balance and storage information.

Check Document Exists

Tool to check if a signed or unsigned document still exists on the OKSign platform.

Remove Document

Tool to remove a signed or unsigned document from the OKSign platform.

Upload Document

Tool to upload a PDF or Word document to OKSign platform for completion and/or signing.

Create Editor Express Session

Tool to invoke the OKSign Editor Express for modifying documents and form descriptors.

Upload Form Descriptor

Tool to upload form descriptor defining signature fields and other field types to a document.

Get Active Documents

Tool to retrieve all active document IDs and properties from OKsign account.

Retrieve Linked Document List

Tool to retrieve the list of linked signed or source document IDs related to a specific document.

Upload Notifications

Tool to upload notifications defining email(s) and/or SMS(es) to be sent to signer(s) with signing links.

Update Organization Token Info

Tool to update organizational token information and settings for the account.

Remove SignExpress Token

Tool to remove a previously uploaded SignExpress tokeninfo JSONObject from the OKSign platform.

Retrieve Users

Tool to retrieve the list of users associated with the OkSign account.

FAQ

Frequently asked questions

With a standalone Oksign MCP server, the agents and LLMs can only access a fixed set of Oksign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Oksign and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Oksign tools.

Yes, absolutely. You can configure which Oksign scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Oksign data and credentials are handled as safely as possible.

Start with Oksign.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Oksign tool your agent needs.Free to start.

Start building