How to integrate Bart MCP with Codex

Framework Integration Gradient
Bart Logo
Codex Logo
divider

Introduction

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

The Bart MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to BART's public transit data. It provides structured and secure access to real-time schedules, route information, station details, and service advisories, so your agent can plan trips, fetch live updates, check advisories, and explore routes for you.

  • Trip planning with live schedules: Instantly retrieve train arrival or departure times and help users plan journeys between any BART stations based on the latest schedule data.
  • Live service advisories and alerts: Keep travelers informed by fetching up-to-date system-wide or station-specific service advisories, ensuring users know about delays or disruptions before they travel.
  • Route and station discovery: Access detailed information about BART routes and stations, including amenities and configuration, so your agent can answer travel questions or recommend stations.
  • Real-time trip and schedule updates: Get the latest trip updates and schedule changes in real time, allowing users to adapt plans quickly if there are changes or issues along their route.
  • Access to static and GTFS feeds: Download the latest BART GTFS (General Transit Feed Specification) data for offline schedule planning, analysis, or integration with third-party transit tools.

Supported Tools & Triggers

Tools
Get BART API VersionStub action for bart api version retrieval.
Get BART Available SchedulesTool to retrieve a list of currently released bart schedules.
Get Route InfoTool to fetch detailed information about a specific bart route.
Get BART StationsStub action for bart stations retrieval.
Get GTFS-RT Trip UpdatesTool to fetch real-time trip updates in gtfs-realtime format.
Download GTFS Static Schedule FeedTool to download the static gtfs feed (google transit.
Get BART Schedule ArriveTool to retrieve schedule information based on a specified arrival time.
Get BART Schedule DepartTool to get schedule information based on a specified depart time.
Get Service AdvisoriesTool to fetch current bart service advisories.
Get Station InfoTool to fetch detailed information for a specified bart station.

Conclusion

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

How to build Bart MCP Agent with another framework

FAQ

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

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

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

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