How to integrate DeployHQ MCP with Codex

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

Introduction

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

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

Supported Tools & Triggers

Tools
Delete CommandTool to delete a command from a specified project.
Delete ProjectTool to delete a project from DeployHQ.
Delete Build Cache FileTool to delete an existing build cache file from a project.
Delete Excluded File RuleTool to delete an existing excluded file rule from a project.
Delete Server GroupTool to delete a server group from a project using the DeployHQ API.
Delete TemplateTool to delete a template by its unique permalink.
Get ProjectsTool to retrieve all projects from DeployHQ account.
Get ProjectTool to view an existing project in DeployHQ.
Get Project Build Known HostsTool to list all known hosts within a project using DeployHQ API.
Get Project CommandsTool to retrieve all SSH commands configured for a project.
Get Project Config FilesTool to retrieve a list of all config files in a DeployHQ project.
Get Project DeploymentsTool to retrieve a paginated list of all deployments in a project.
Get Project Excluded FilesTool to list all excluded files within a project template.
Get Config FileTool to view a specific config file in a DeployHQ project.
Get Excluded FileTool to view a specific excluded file in a DeployHQ project.
Get Server GroupTool to view a specific server group in a DeployHQ project.
Get Project RepositoryTool to view repository details for a specific project in DeployHQ.
Get Repository BranchesTool to view all available branches in the connected repository for a project.
Get Repository Commit InfoTool to view detailed information about a specific revision in a project's connected repository.
Get Latest Repository RevisionTool to view the latest remote revision of your repository.
Get Recent Commits and TagsTool to view up to 15 most recent revisions and up to 15 most recent tags in a specific branch.
Get Project Scheduled DeploymentsTool to retrieve all upcoming scheduled deployments for a project.
Get Project Server GroupsTool to retrieve all server groups configured for a project.
Get Project ServersTool to retrieve all servers configured for a project.
Get TemplatesTool to retrieve all templates from DeployHQ account.
Get Public TemplateTool to retrieve a specific public template from DeployHQ.
Get Public TemplatesTool to retrieve publicly available deployment templates from DeployHQ.
Update ProjectTool to update project settings in DeployHQ.
Update Build Cache FileTool to update an existing build cache file in a project.
Update Build CommandTool to update an existing build command in a project.
Update Language VersionTool to update the version of a language in a project's build environment.
Update Project CommandTool to update an existing SSH command in a project.
Update Config FileTool to update an existing config file in a DeployHQ project.
Update Excluded FileTool to update an existing excluded file rule in a project.
Update Project RepositoryTool to update repository configuration for a project in DeployHQ.
Update Server GroupTool to update an existing server group in a DeployHQ project.
Update TemplateTool to update an existing template in DeployHQ.
Create ProjectTool to create a new project in DeployHQ.
Generate AI Deployment OverviewTool to generate an AI-powered deployment overview for a revision range.
Create Build Cache FileTool to create a new build cached file within a project.
Create Build CommandTool to create a new build command for a project in DeployHQ.
Create Project Build Known HostTool to create a new known host in a project using DeployHQ API.
Create SSH CommandTool to create a new SSH command for a project in DeployHQ.
Create Config FileTool to create a new config file in a DeployHQ project.
Create Config File DeploymentTool to create a new config file deployment for a project.
Create Excluded FileTool to add a new excluded file to a project.
Abort DeploymentTool to abort a currently running deployment.
Add Project RepositoryTool to add repository details to a project in DeployHQ.
Create Server GroupTool to create a new server group for automated deployments in a DeployHQ project.
Create ServerTool to create a new server configuration in a DeployHQ project.
Create TemplateTool to create a new template in DeployHQ.
Update Project SettingsTool to update settings of an existing DeployHQ project.
Edit Build Cache FileTool to edit an existing build cache file within a project.
Edit Build CommandTool to edit an existing build command within a template in DeployHQ.
Edit SSH CommandTool to edit an existing SSH command in a DeployHQ project.
Edit Config FileTool to edit an existing config file within a project.
Edit Excluded FileTool to edit an existing excluded file rule within a project.
Update Excluded FileTool to update an existing excluded file rule in a project.
Update Project RepositoryTool to update repository details for an existing project in DeployHQ.
Update Server GroupTool to update a server group in a DeployHQ project using the API.
Edit TemplateTool to edit an existing template in DeployHQ.

Conclusion

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

How to build DeployHQ MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use DeployHQ MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use DeployHQ MCP with Claude Agent SDK

Google ADK

Google ADK

Use DeployHQ MCP with Google ADK

LangChain

LangChain

Use DeployHQ MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use DeployHQ MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use DeployHQ MCP with Mastra AI

LlamaIndex

LlamaIndex

Use DeployHQ MCP with LlamaIndex

CrewAI

CrewAI

Use DeployHQ MCP with CrewAI

Claude Code

Claude Code

Use DeployHQ MCP with Claude Code

FAQ

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

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

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

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