How to integrate Crustdata MCP with Codex

GET STARTED FOR FREE
Crustdata logo
Codex logo
divider

Introduction

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

Also integrate Crustdata 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 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 Crustdata 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 connect.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 Crustdata MCP server, and what's possible with it?

The Crustdata MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Crustdata account. It provides structured and secure access to real-time company and people intelligence, so your agent can perform actions like lead enrichment, market research, investor portfolio analysis, and workforce trend tracking on your behalf.

  • Comprehensive person and company enrichment: Instantly enrich leads or companies with up-to-date details for customer profiling, data verification, or targeted outreach.
  • Advanced decision maker filtering: Find and analyze decision makers across organizations using complex filters, titles, and segmentation for your sales or marketing efforts.
  • Investor portfolio and funding milestone analysis: Retrieve in-depth investor portfolio data, analyze funding milestones, and generate reports for investment research or deal sourcing.
  • Workforce and job market trend insights: Fetch headcount and job listing timeseries data to track organizational growth, hiring activity, or competitive shifts in specific industries.
  • Social and web activity monitoring: Collect and analyze LinkedIn posts and web traffic data for any company to assess engagement, sentiment, and digital footprint for market intelligence and outreach strategies.

Supported Tools & Triggers

Tools
Enrich person screenerThe screener person enrich endpoint enriches person data by providing additional information based on the given query.
Fetch headcount by facet timeseriesRetrieves headcount data as a timeseries with faceted analysis capabilities.
Fetch investor portfolio dataRetrieves comprehensive investor portfolio data from the data lab section of the crustdata api.
Filter decision makers dataFilters and retrieves decision maker data from the crustdata b2b saas integration platform based on complex criteria.
Post funding milestone timeseries dataThe fundingmilestonetimeseries endpoint retrieves time-series data related to funding milestones for companies.
Post headcount timeseries dataRetrieves filtered and sorted headcount timeseries data from the crustdata data lab.
Post job listings table dataThis endpoint retrieves filtered and sorted job listings data for specified company tickers from a chosen dataset in the crustdata platform.
Post web traffic dataRetrieves filtered and sorted web traffic data from the crustdata platform.
Retrieve linkedin postsRetrieves linkedin posts for a specified company using crustdata's screener functionality.
Screener company informationThe getcompanyscreener endpoint allows users to search and filter companies based on various criteria such as headcount, growth rate, funding, and more.
Screen metrics and filter conditionsThe screendata endpoint enables advanced data screening and filtering on the crustdata platform.
Search companies with filtersThe companysearch endpoint enables users to search and filter companies using the crustdata api.
Search for job id in screenerThe screener person search endpoint allows users to search for persons associated with a specific job id within the crustdata b2b saas integration platform.
Search linkedin posts by keywordThis endpoint enables searching for linkedin posts using a specific keyword.

Conclusion

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

How to build Crustdata MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Crustdata MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Crustdata MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Crustdata MCP with Claude Code

OpenClaw logo

OpenClaw

Use Crustdata MCP with OpenClaw

CLI logo

CLI

Use Crustdata MCP with CLI

Google ADK logo

Google ADK

Use Crustdata MCP with Google ADK

LangChain logo

LangChain

Use Crustdata MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Crustdata MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Crustdata MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Crustdata MCP with LlamaIndex

CrewAI logo

CrewAI

Use Crustdata MCP with CrewAI

FAQ

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

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

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

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