How to integrate Conveyor MCP with Codex

Framework Integration Gradient
Conveyor Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Conveyor 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 Conveyor 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 Conveyor MCP server, and what's possible with it?

The Conveyor MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Conveyor account. It provides structured and secure access to your security reviews and compliance workflows, so your agent can perform actions like retrieving documents, managing authorization requests, tracking connections, and automating security questionnaire processes on your behalf.

  • Authorization request management: Fetch, list, and review details of all authorization requests, making it easy for your agent to help you track and respond to security and compliance requests in real time.
  • Document and folder automation: Retrieve, organize, or delete specific documents and folders, ensuring your Trust Center stays tidy and up to date without manual effort.
  • Connection insights and tracking: Access a complete list of your Conveyor connections, letting your agent monitor integrations and stay on top of your security ecosystem.
  • Interaction history by document: Instantly pull all interactions related to a specific document, so your agent can summarize or audit user activity for compliance needs.
  • API token validation and guidance: Use AI-driven guidance to validate API tokens and get structured support for access issues, helping keep your Conveyor integration secure and running smoothly.

Supported Tools & Triggers

Tools
Delete a Conveyor documentTool to delete a specific document.
Delete folderTool to delete a folder by its ID.
Generate/Validate API Token GuidanceTool to validate API token and provide guidance.
Get Authorization RequestTool to fetch details of a specific authorization request.
Get Authorization RequestsTool to fetch authorization requests.
Get all authorization requestsTool to retrieve all authorization requests.
Get all Conveyor connectionsTool to retrieve all connections.
Get all Conveyor documentsTool to retrieve all documents.
Get all Conveyor foldersTool to retrieve all folders.
Get interactions by document IDTool to fetch interactions associated with a specific document.
Get Knowledge Base QuestionsTool to retrieve knowledge base questions.
Get product linesTool to fetch all product lines.
Patch authorizationTool to update or revoke an existing authorization.
Patch Conveyor documentTool to update document attributes.
Create new authorizationTool to create a new authorization.
Upload new documentTool to upload a new document.
Create new folderTool to create a new folder in Conveyor Exchange.
Submit single questionTool to submit a single question.

Conclusion

You've successfully integrated Conveyor with Codex using Composio's Rube MCP server. Now you can interact with Conveyor 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 Conveyor 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 Conveyor operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Conveyor MCP Agent with another framework

FAQ

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

With a standalone Conveyor MCP server, the agents and LLMs can only access a fixed set of Conveyor tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Conveyor 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 Conveyor tools.

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

Yes, absolutely. You can configure which Conveyor 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 Conveyor 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.