How to integrate Studio By Ai21 Labs MCP with Codex

Framework Integration Gradient
Studio By Ai21 Labs Logo
Codex Logo
divider

Introduction

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

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

Supported Tools & Triggers

Tools
Check Can IframeTool to check if a URL can be embedded in an iframe.
Compare TextTool to compare two text strings and identify differences.
Create Aftersales Parts Classification BatchTool to create a batch job for Fnac Aftersales parts classification.
Create Assistant RouteTool to create a new route for an AI21 Studio assistant.
Create AssistantTool to create a new AI assistant in AI21 Studio.
Create Assistant PlanTool to create a new plan for an AI21 Studio assistant.
Create DemoTool to create a new demo in AI21 Studio.
Generate RequirementsTool to generate requirements from a query or task description.
Generate Thread NameTool to generate a thread name from a query or conversation context.
Create Kirsh Grant Compliance PreviewTool to preview grant compliance for Kirsh grants.
Kirsh Grant Metadata PreviewTool to retrieve grant metadata from the Kirsh preview endpoint.
Create MCP StorageTool to create MCP (Model Context Protocol) storage in AI21 Studio.
Create SecretTool to save a secret in AI21 Studio.
Check Kirsh Grant ComplianceTool to check compliance for Kirsh grant IDs.
Create Website ConnectorTool to create a website connector in AI21 Studio.
Delete AssistantTool to delete an assistant by its unique ID.
Delete Assistant RouteTool to delete a route from an AI21 Studio assistant.
Delete DemoTool to delete a demo by its unique ID.
Delete MCP StorageTool to delete an MCP (Model Context Protocol) storage configuration by its unique ID.
Delete SecretTool to delete a secret by its unique ID.
Delete Website ConnectorPermanently delete a website connector by its unique identifier.
Download Modified DocumentTool to download a modified document from AI21 Labs Studio.
Get AssistantTool to retrieve an assistant by its unique identifier.
Get Assistant RouteTool to retrieve details of a specific route for an AI21 Studio assistant.
Get Assistants By MCPTool to retrieve all assistants associated with a specific MCP (Model Context Protocol) storage configuration.
Get Batch Prediction StatusTool to check the status of a Fnac Aftersales parts classification batch prediction job.
Get DemoTool to retrieve a demo by its unique ID.
Grant Kirsh MetadataTool to retrieve Kirsh grant metadata by grant ID.
Get Library Batch StatusTool to get the ingestion status of a library batch.
Get MCP StorageTool to retrieve a specific MCP (Model Context Protocol) storage configuration by its unique ID.
Get Output ExplanationTool to get output explanation for an execution (cached or generated).
Get PlanTool to retrieve a specific plan from an AI21 Studio assistant.
Get Website Connector By IDTool to retrieve details of a specific website connector by its ID.
Get Website Connector StatusTool to retrieve the status of a website connector ingestion.
Get Website Connector URL StatusTool to retrieve the status of a specific URL in the website connector.
Ingest Website ConnectorTool to ingest website content via sitemap URL in AI21 Studio.
Ingest Website Connector URLTool to ingest a website URL into AI21 Studio's website connector.
List AssistantsTool to retrieve all assistants from AI21 Studio.
List Website ConnectorsTool to retrieve website connector information from AI21 Studio.
List DemosTool to retrieve all demos from AI21 Studio.
List Library FilesTool to list files in the workspace library with optional filtering.
List MCP StorageTool to retrieve all MCP (Model Context Protocol) storage configurations from AI21 Studio.
List ModelsTool to retrieve information about all available AI21 models.
List PlansTool to list all plans for a specific assistant.
List SecretsTool to retrieve all secrets from AI21 Studio secret storage.
List Workspace ModelsTool to retrieve all workspace models by organization from AI21 Studio.
List Available ModelsTool to retrieve all available models from AI21 Studio settings.
Modify AssistantTool to modify an existing AI21 Studio assistant.
Modify Assistant RouteTool to modify an existing route within an assistant.
Modify Assistant PlanTool to modify an existing assistant plan in AI21 Studio.
Retry Ingest WebsiteTool to retry ingestion of a website in AI21 Studio.
Run AssistantTool to run an AI21 Studio assistant with conversational input.
Sync Website ConnectorTool to sync a website connector in AI21 Studio.
Update DemoTool to update an existing demo in Studio by AI21 Labs.
Update MCP StorageTool to update an existing MCP (Model Context Protocol) storage configuration in AI21 Studio.
Update SecretTool to update an existing secret in AI21 Studio.
Validate PlanTool to validate Python code for an AI21 Studio assistant plan.

Conclusion

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

How to build Studio By Ai21 Labs MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Studio By Ai21 Labs MCP?

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

Can I manage the permissions and scopes for Studio By Ai21 Labs while using Tool Router?

Yes, absolutely. You can configure which Studio By Ai21 Labs 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 Studio By Ai21 Labs 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.