How to integrate Moco MCP with Codex

Framework Integration Gradient
Moco Logo
Codex Logo
divider

Introduction

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

The Moco MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Moco account. It provides structured and secure access to your business and project management data, so your agent can manage time tracking, handle deals, organize contacts, and update project activities on your behalf.

  • Automated time tracking and activity management: Let your agent list, retrieve, and update time entries, so tracking billable hours and project work is effortless.
  • Deal and pipeline automation: Ask your agent to fetch deal details, delete obsolete deals, or reference available deal categories to keep your sales pipeline up to date.
  • Comprehensive contact and company organization: Have your agent list contacts, add new companies, or delete companies as your business relationships evolve.
  • Comment retrieval for collaboration: Retrieve and review comments on various resources, helping your team stay in sync and informed.
  • Flexible project and resource control: Use your agent to access and manage project-related information, so you can stay organized without manual data entry.

Supported Tools & Triggers

Tools
List ActivitiesTool to retrieve activities.
Get ActivityTool to retrieve a single activity by id.
Update ActivityTool to update an existing activity.
List commentsTool to retrieve a list of comments.
Create CompanyTool to create a new company.
Delete a companyTool to delete a company.
List ContactsTool to retrieve a list of contacts.
List Deal CategoriesTool to list deal categories with their ids and probabilities.
Delete DealTool to delete a deal.
Get DealTool to retrieve a single deal by id.
List DealsTool to retrieve a list of all deals (leads).
Update DealTool to update an existing deal.
List InvoicesTool to retrieve a list of all invoices.
Create InvoiceTool to create a new invoice.
Create PurchaseTool to create a new purchase.
Get OfferTool to retrieve a single offer by id.
List OffersTool to retrieve a list of all offers.
List Planning EntriesTool to retrieve a list of all planning entries.
Create Planning EntryTool to create a new planning entry.
Get Planning EntryTool to retrieve a single planning entry by id.
Create ProjectTool to create a new project in moco.
Get ProjectTool to retrieve a single project by id.
List ProjectsTool to retrieve a list of all projects.
Update ProjectTool to update an existing project.
List UsersTool to list all users.

Conclusion

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

How to build Moco MCP Agent with another framework

FAQ

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

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

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

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