How to integrate Gleap MCP with Codex

Framework Integration Gradient
Gleap Logo
Codex Logo
divider

Introduction

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

The Gleap MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Gleap account. It provides structured and secure access to your customer feedback data, so your agent can perform actions like managing support tickets, communicating with users, organizing help center content, and handling team workflows on your behalf.

  • Ticket creation and management: Instantly create new support tickets, archive resolved issues, or retrieve existing tickets to streamline customer support workflows.
  • Chat and user communication: Allow your agent to send new chat messages or fetch entire chat histories, making it easy to keep conversations going with users.
  • Help center organization: Create collections or retrieve articles in your help center, enabling your agent to help manage and organize your knowledge base content efficiently.
  • Team and user administration: Add new teams for ticket assignment or remove users from projects, so you can stay on top of team management tasks without lifting a finger.
  • Checklist and engagement tracking: Fetch detailed checklists to monitor user engagement or onboarding progress, giving your agent context to provide personalized support.

Supported Tools & Triggers

Tools
Archive a TicketTool to archive a ticket.
Create a CollectionTool to create a help center collection.
Create a new chat messageTool to create a new chat message.
Create a new teamTool to create a new team.
Create a new ticketTool to create a new ticket.
Delete a User from a ProjectTool to remove a user from a project.
Get a ChecklistTool to retrieve a specific engagement checklist by its ID.
Get a CollectionTool to retrieve a help center collection by ID.
Get all articlesTool to retrieve all articles in a help center collection.
Get all chat messagesTool to retrieve all chat messages.
Get All CollectionsTool to retrieve all help center collections.
Get All Invitations for a ProjectTool to retrieve all invitations for a project.
Get all sessionsTool to retrieve all sessions for the current project.
Get All TeamsTool to retrieve all teams.
Get All TicketsTool to retrieve all tickets.
Get All Users for a ProjectTool to retrieve all users for a project.
Get a ticketTool to retrieve a specific ticket by its ID.
Get current userTool to retrieve the currently authenticated user's details.
Get Help Center SourcesTool to retrieve available help center sources.
Get notification ticketTool to retrieve a notification ticket using its share token.
Get session checklistsTool to retrieve checklists for a given session.
Identify or update userTool to identify or update user information.
Link a TicketTool to link a ticket.
Search for TicketsTool to search for tickets.
Track eventsTool to track server-side customer events.
Unarchive a TicketTool to unarchive a ticket.
Unlink a TicketTool to unlink a ticket.
Update a User for a ProjectTool to update a user’s role in a project.
Update Chat MessageTool to update a chat message.

Conclusion

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

How to build Gleap MCP Agent with another framework

FAQ

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

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

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

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