How to integrate Rkvst MCP with Codex

Framework Integration Gradient
Rkvst Logo
Codex Logo
divider

Introduction

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

The Rkvst MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Rkvst account. It provides structured and secure access to your supply chain evidence data, so your agent can perform actions like retrieving asset details, verifying event authenticity, downloading attachments, and managing chain of custody records on your behalf.

  • Asset and event retrieval: Instantly fetch detailed information about assets, events, or public assets by their unique identifiers, including historical state data.
  • Chain of custody verification: Have your agent review event metadata and associated trails to ensure data authenticity and transparency throughout your supply chain.
  • Download evidence attachments: Let your agent securely download raw binary attachments associated with supply chain events for auditing or record-keeping.
  • App and member inspection: Effortlessly pull configuration and credential details for app registrations or retrieve member and IAM subject information to monitor access and permissions.
  • Tenancy and blob management: Retrieve tenancy details or access specific data blobs related to your supply chain records for better oversight and control.

Supported Tools & Triggers

Tools
Download Event AttachmentTool to download an attachment from a specified event on an asset.
Get App RegistrationTool to retrieve details for a given app registration id.
Get AssetTool to retrieve details for a given asset.
Get BlobTool to retrieve details of a blob by id.
Get EventTool to retrieve details of a specified event.
Get IAM SubjectTool to retrieve iam subject details.
Get MemberTool to retrieve details for a given member id.
Get Public AssetTool to retrieve details for a public asset.
Get Public Asset EventTool to retrieve a specific public asset event.
Get TenancyTool to retrieve details for a specific tenancy.
List App RegistrationsTool to list all app registrations.
List Asset EventsTool to list events for a specified asset.
List AssetsTool to list all assets with optional pagination and filters.
List IAM SubjectsTool to list iam subjects.
List MembersTool to list all tenant members.
List Public Asset EventsTool to list events for a specific public asset.
List Public AssetsTool to list all public assets.
List TenanciesTool to list all tenancies.
Promote MemberTool to promote a tenant member to owner role.
Retrieve asset attachment metadataTool to retrieve metadata for an attachment on a specified asset.
Retrieve CapsTool to retrieve resource limit quotas for a specified service.
Retrieve Event Attachment MetadataTool to retrieve metadata for an attachment on a specified event.
Retrieve Public Asset Attachment MetadataTool to retrieve metadata for an attachment on a specified public asset.
Retrieve Public Event Attachment MetadataTool to retrieve metadata for an attachment on a public asset event.
Search EventsTool to search events matching filter criteria with pagination.
Update App RegistrationTool to update an application's display name or custom claims.

Conclusion

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

How to build Rkvst MCP Agent with another framework

FAQ

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

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

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

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