How to integrate Refiner MCP with Codex

Refiner logo
Codex logo
divider

Introduction

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

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

The Refiner MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Refiner account. It provides structured and secure access to your customer feedback and survey data, so your agent can perform actions like fetching contacts, analyzing survey responses, managing user segments, updating user data, and generating reports on your behalf.

  • Contact management and updates: Effortlessly retrieve, update, or delete contact records, allowing your agent to keep user data clean and up-to-date.
  • Survey and form discovery: Instantly list all surveys or forms in your Refiner account, filter by state, and access their configurations for deeper analysis or reporting.
  • Survey response retrieval and analytics: Pull in all survey responses, filter results, and generate detailed analytics or reporting to uncover actionable insights from your customer feedback.
  • User segmentation and targeting: Fetch and browse user segments, enabling your agent to target specific groups for outreach or further analysis based on collected data.
  • Event tracking and behavioral logging: Automatically record user events, associate them with contacts, and enrich feedback data for advanced behavioral analytics.

Supported Tools & Triggers

Tools
Delete ContactTool to delete a specific contact by its identifier.
Get Account InfoTool to fetch refiner account subscription and environment usage details.
Get ContactTool to retrieve details of a specific contact by its id.
Get ContactsTool to retrieve a list of contacts from your refiner account.
Get FormsTool to retrieve a list of forms (surveys) from your refiner account with optional filtering and pagination.
Get ReportingTool to retrieve aggregated reporting data for surveys including metrics and analytics.
Get Survey ResponsesTool to retrieve all survey responses from your refiner account with optional filtering and pagination.
Get SegmentsTool to retrieve a list of user segments from your refiner account.
Track EventTool to record a user event by name for a user identified via user id or email.
Update ContactTool to update an existing contact's attributes or account.

Conclusion

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

How to build Refiner MCP Agent with another framework

FAQ

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

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

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

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