How to integrate Wit ai MCP with Codex

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Wit ai logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Wit ai MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Wit ai with

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 1000+ 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 Wit ai MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Wit ai MCP server, and what's possible with it?

The Wit ai MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Wit ai account. It provides structured and secure access to your NLP resources, so your agent can create and manage apps, analyze natural language, organize intents and traits, and update configurations on your behalf.

  • Instant natural language analysis: Let your agent extract intents, entities, and traits from any text message using Wit.ai’s advanced NLP engine.
  • Automated app management: Easily create, update, or delete Wit.ai apps, enabling rapid deployment and maintenance of your language models.
  • Intent and trait organization: Have your agent list, retrieve details, or update all defined intents and traits, keeping your language understanding models organized and up to date.
  • Full app metadata access: Fetch comprehensive app settings and metadata for better monitoring, debugging, or auditing of your NLP solutions.
  • Seamless entity and trait customization: Programmatically add or configure traits for tailored entity recognition and improved intent matching.

Supported Tools & Triggers

Tools
Add Entity KeywordTool to add a keyword with optional synonyms to a Wit.
Add Keyword SynonymTool to add a new synonym to a keyword in an entity.
Add Value to TraitTool to add a new value to an existing trait in Wit.
Create Wit.ai AppTool to create a new app in Wit.
Create Wit.ai EntityTool to create a new entity in Wit.
Create Wit.ai IntentTool to create a new intent in Wit.
Create Wit.ai TraitTool to create a new trait in Wit.
Create Wit.ai Training UtterancesTool to add training utterances (samples with annotations) to your Wit.
Delete AppTool to delete a specific app from wit.
Delete EntityTool to permanently delete an entity by name.
Delete Entity KeywordTool to delete a keyword from a keywords entity in wit.
Delete Entity RoleTool to delete a specific role from an entity in wit.
Delete IntentTool to permanently delete an intent by name.
Delete Keyword SynonymTool to delete a synonym from a keyword in an entity.
Delete UtterancesTool to delete validated utterances (training samples) from your Wit.
Wit.ai Detect LanguageTool to detect the language of a given text input.
Export App DataTool to export Wit.
Get App DetailsTool to retrieve metadata and settings of a Wit.
Get Entity DetailsTool to retrieve details of a specific entity including keywords and roles.
Get Intent DetailsTool to retrieve details of a specific intent.
Get IntentsTool to list all intents in a Wit.
Wit.ai Get MessageTool to analyze a text message and extract its intent, entities, and traits.
Get Trait DetailsTool to retrieve details of a specific trait.
List TraitsTool to list all traits in a Wit.
Get Voice DetailsTool to retrieve details for a specific text-to-speech voice.
List Wit.ai AppsTool to retrieve the list of all Wit.
List App TagsTool to retrieve all tag groups (versions) for a Wit.
List EntitiesTool to list all entities in a Wit.
List UtterancesTool to retrieve training utterances (samples) from a Wit.
List VoicesTool to retrieve all available text-to-speech voices grouped by locale.
Update Wit.ai AppTool to update an existing Wit.

Conclusion

You've successfully integrated Wit ai with Codex using Composio's MCP server. Now you can interact with Wit ai 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 Wit ai operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Wit ai operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Wit ai MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Wit ai MCP?

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

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

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