How to integrate Oksign MCP with Codex

GET STARTED FOR FREE
Framework Integration Gradient
Oksign Logo
Codex Logo
divider

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 app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

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 870+ 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

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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.

Supported Tools & Triggers

Tools
Remove BriefcaseTool to remove a previously created briefcase from OKSign platform.
Retrieve Briefcase InformationTool to retrieve a previously uploaded briefcase tokeninfo for consultation.
Remove ContactsTool to remove specified contacts from the account's contact list.
Retrieve ContactsTool to retrieve the list of contacts stored in the account.
Upload ContactsTool to insert or update contact information in the account's contact list.
Retrieve Account CreditsTool to retrieve account credit balance and storage information.
Check Document ExistsTool to check if a signed or unsigned document still exists on the OKSign platform.
Remove DocumentTool to remove a signed or unsigned document from the OKSign platform.
Upload DocumentTool to upload a PDF or Word document to OKSign platform for completion and/or signing.
Create Editor Express SessionTool to invoke the OKSign Editor Express for modifying documents and form descriptors.
Upload Form DescriptorTool to upload form descriptor defining signature fields and other field types to a document.
Get Active DocumentsTool to retrieve all active document IDs and properties from OKsign account.
Retrieve Linked Document ListTool to retrieve the list of linked signed or source document IDs related to a specific document.
Upload NotificationsTool to upload notifications defining email(s) and/or SMS(es) to be sent to signer(s) with signing links.
Update Organization Token InfoTool to update organizational token information and settings for the account.
Remove SignExpress TokenTool to remove a previously uploaded SignExpress tokeninfo JSONObject from the OKSign platform.
Retrieve UsersTool to retrieve the list of users associated with the OkSign account.

Conclusion

You've successfully integrated Oksign with Codex using Composio's Rube 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's Rube
  • Access to 20,000+ tools across 870+ 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

How to build Oksign MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Oksign MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Oksign MCP with Claude Agent SDK

Google ADK

Google ADK

Use Oksign MCP with Google ADK

LangChain

LangChain

Use Oksign MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Oksign MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Oksign MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Oksign MCP with LlamaIndex

CrewAI

CrewAI

Use Oksign MCP with CrewAI

Claude Code

Claude Code

Use Oksign MCP with Claude Code

FAQ

What are the differences in Tool Router MCP and Oksign MCP?

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.

Can I use Tool Router MCP with Codex?

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.

Can I manage the permissions and scopes for Oksign while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free