How to integrate Modelry MCP with Codex

Framework Integration Gradient
Modelry Logo
Codex Logo
divider

Introduction

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

The Modelry MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Modelry account. It provides structured and secure access to your machine learning model management, so your agent can perform actions like listing modeling requests, creating workspaces, retrieving embed details, and managing products on your behalf.

  • Workspace management: Easily create new workspaces or fetch details about existing ones to keep your projects organized and separated.
  • Embed and product operations: List all available embeds, get detailed information, or delete embeds and products as needed for smooth deployment and maintenance.
  • Repository handling: Retrieve details of product repositories or remove repositories you no longer need—all with structured agent commands.
  • Modeling request tracking: Quickly list all 3D modeling requests tied to your account to monitor progress and manage workflows efficiently.
  • Secure automated actions: Let your agent handle repetitive or administrative model management tasks securely, saving you time and effort.

Supported Tools & Triggers

Tools
Create WorkspaceTool to create a new workspace.
Delete Modelry EmbedTool to delete an embed.
Delete Modelry ProductTool to delete a product.
Delete Product RepositoryTool to delete a product repository.
Delete Modelry WorkspaceTool to delete a workspace.
Get EmbedTool to retrieve details of a specific embed.
Get Product RepositoryTool to retrieve details of a specific product repository.
Get WorkspaceTool to retrieve details for a specific workspace.
List EmbedsTool to list available embeds.
List Modeling RequestsTool to list all 3d modeling requests associated with the authenticated user's workspace.
List Product RepositoriesTool to list all product repositories in a workspace.
List Modelry ProductsTool to list all products in modelry.
List Modelry WorkspacesTool to list all workspaces in modelry.
Order Modeling ServiceTool to place an order for 3d modeling services.
Track Modeling ProgressTool to track the progress of a 3d modeling request.

Conclusion

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

How to build Modelry MCP Agent with another framework

FAQ

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

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

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

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