How to integrate Ragie MCP with Codex

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

Introduction

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

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

Supported Tools & Triggers

Tools
Create DocumentTool to upload and process a document file in Ragie.
Create Document From URLTool to ingest a document from a publicly accessible URL.
Create Document RawTool to ingest a document as raw text or JSON.
Create InstructionTool to create a new instruction that applies natural language directives to documents as they're ingested or updated.
Create OAuth Redirect URLTool to create an OAuth redirect URL for initializing embedded connector OAuth flows.
Create PartitionTool to create a new partition for scoping documents and connections in Ragie.
Delete DocumentTool to delete a document from Ragie.
Delete InstructionTool to delete an instruction and all associated entities.
Delete PartitionTool to delete a partition and all associated data irreversibly.
Get DocumentTool to retrieve a specific document by its unique identifier.
Get Document ChunkTool to retrieve a specific document chunk by its document and chunk ID.
Get Document Chunk ContentTool to retrieve document chunk content in requested format with streaming support for media.
Get Document ChunksTool to retrieve document chunks with pagination support.
Get Document ContentTool to retrieve the content of a document by its ID.
Get Document SummaryTool to retrieve an LLM-generated summary of a document by its ID.
Get PartitionTool to retrieve a partition by ID with usage statistics and resource limits.
Get ResponseTool to retrieve a response by its unique identifier.
List ConnectionsTool to list all connections sorted by creation date descending with pagination support.
List Connection Source TypesTool to list available connection source types like 'google_drive' and 'notion' along with their metadata.
List DocumentsTool to list all documents sorted by creation date (descending) with pagination support.
List Entities By DocumentTool to retrieve all extracted entities from a specific document with pagination support.
List Entities by InstructionTool to retrieve entities generated by a specific instruction.
List InstructionsTool to retrieve all instruction records from the Ragie system.
List PartitionsTool to retrieve a paginated list of all partitions sorted by name in ascending order.
Patch Document MetadataTool to update metadata for a specific document with partial update support.
Retrieve Document ChunksTool to retrieve relevant document chunks based on a query.
Set Partition LimitsTool to set usage limits on partition pages and media.
Update Document From URLTool to update an existing document by fetching content from a publicly accessible URL.
Update Document RawTool to update a document's content from raw text or JSON data.
Update InstructionTool to update an instruction's active status.
Update PartitionTool to update a partition's configuration including description, context-aware settings, and metadata schema.

Conclusion

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

How to build Ragie MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Ragie MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Ragie MCP with Claude Agent SDK

Google ADK

Google ADK

Use Ragie MCP with Google ADK

LangChain

LangChain

Use Ragie MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Ragie MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Ragie MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Ragie MCP with LlamaIndex

CrewAI

CrewAI

Use Ragie MCP with CrewAI

Claude Code

Claude Code

Use Ragie MCP with Claude Code

FAQ

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

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

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

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