How to integrate Botstar MCP with Codex

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Botstar logo
Codex logo
divider

Introduction

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

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

The Botstar MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Botstar account. It provides structured and secure access to your chatbot operations, so your agent can perform actions like managing live chat sessions, updating user details, retrieving app parameters, and sending data between webviews and your bot—all on your behalf.

  • Live chat session control: Programmatically open, close, or reinitialize the Botstar live chat widget to manage user interactions in real time.
  • Automated user profile updates: Let your agent update user details and profile attributes during an active chatbot conversation for a more personalized experience.
  • Webview data exchange: Seamlessly send responses from webviews back to the chatbot or retrieve parameters passed from the bot to your webview for dynamic content handling.
  • Custom callback registration: Set up onOpen and onClose event handlers so your agent can trigger actions whenever users interact with the chat window.
  • Application ID and configuration retrieval: Fetch essential Botstar application IDs and parameters for smooth widget initialization and advanced bot customization.

Supported Tools & Triggers

Tools
Create BotTool to create a new bot in BotStar.
Create Bot AttributeTool to create a new bot attribute in BotStar.
Create CMS EntityTool to create a CMS entity in BotStar with a name and optional fields.
Create Entity FieldsTool to create entity field(s) in BotStar CMS.
Create Entity ItemTool to create a new entity item in BotStar CMS.
Create User AttributesTool to create custom user attributes in BotStar.
Delete Bot AttributeTool to delete a bot attribute by ID.
Delete CMS EntityTool to delete a CMS entity by ID.
Delete Entity FieldsTool to delete entity field(s) from a CMS entity.
Delete Entity ItemTool to delete an entity item from a CMS entity.
Get BotTool to get your bot by bot ID.
Get BotStar Application IDsTool to retrieve the BotStar application ID (`appId`).
Get CMS EntityTool to get a specific CMS entity by ID.
Get Entity ItemTool to retrieve a specific item from a CMS entity with all field values.
List Bot AttributesTool to get all bot attributes from BotStar.
List BotsTool to get your list of bots.
List CMS EntitiesTool to retrieve all CMS entities for a bot.
List Entity ItemsTool to retrieve all entity items with pagination support.
Livechat bootTool to reinitialize the live chat widget with provided data.
Close BotStar Livechat WidgetTool to hide the live chat window.
BotStar LiveChat onClose CallbackTool to register a callback when the chat window is closed.
Livechat on openTool to register a callback when the chat window is opened.
Livechat openTool to show the live chat window.
Livechat updateTool to update user details on the current live chat session.
Publish Bot to LiveTool to publish a bot to live.
Update Bot AttributeTool to update a bot attribute in BotStar.
Update CMS EntityTool to update a CMS entity in BotStar.
Update Entity FieldsTool to update entity field(s) in BotStar CMS.
Update Entity ItemTool to update a CMS entity item in BotStar.
Get BotStar Webview ParameterTool to retrieve a parameter value passed from the BotStar chatbot to the webview.
Webview send responseTool to send data from the webview back to the BotStar chatbot.

Conclusion

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

How to build Botstar MCP Agent with another framework

FAQ

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

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

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

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