How to integrate Kaggle MCP with Codex

Framework Integration Gradient
Kaggle Logo
Codex Logo
divider

Introduction

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

The Kaggle MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kaggle account. It provides structured and secure access to your Kaggle datasets, competitions, and configurations, so your agent can perform actions like downloading competition data, creating datasets, submitting entries, and managing dataset versions on your behalf.

  • Competition data access and download: Let your agent fetch and download competition datasets quickly by specifying a competition ID, so you always have the latest files for analysis.
  • Automated dataset creation and management: Have your agent create new Kaggle datasets, update metadata, and publish new dataset versions seamlessly, streamlining the process of sharing your work with the community.
  • Competition entry submission: Empower your agent to submit competition entries automatically once your solution is ready and uploaded, helping you participate in challenges without manual hassle.
  • Configuration management and setup: Allow your agent to initialize, locate, and update Kaggle API configuration files and keys, ensuring smooth and authenticated operations every time.
  • Dataset status monitoring: Ask your agent to check the status of uploaded datasets or processing jobs, so you always know when your data is ready for use or public sharing.

Supported Tools & Triggers

Tools
Download competition data filesTool to download competition data files.
Initialize Kaggle ConfigurationTool to initialize Kaggle API client configuration.
Dataset CreateTool to create a new Kaggle dataset with full metadata.
Get Dataset StatusTool to get the status of a dataset upload or processing job.
Create Dataset VersionTool to create a new dataset version on Kaggle.
Submit Competition EntryTool to submit an entry to a Kaggle competition.
Get Kaggle Config DirectoryTool to retrieve the directory of the Kaggle API configuration file.
Get Kaggle Config FileTool to retrieve the filename of the Kaggle API configuration file.
List Kaggle Configuration KeysTool to list local Kaggle API configuration keys.
Get Kaggle Config PathTool to retrieve local Kaggle API configuration file path.
Reset Kaggle ConfigurationTool to reset local Kaggle CLI configuration to defaults.
Set Kaggle ConfigurationTool to set a Kaggle CLI configuration parameter.
Unset Kaggle ConfigurationTool to unset a Kaggle CLI configuration parameter.
View Kaggle ConfigurationTool to view local Kaggle API configuration.
Kaggle Dataset InitTool to initialize a dataset-metadata.
List Kaggle Dataset FilesTool to list files in a Kaggle dataset.
Kaggle Kernel InitTool to initialize a kernel-metadata.
Download kernel outputTool to download the output of a Kaggle kernel.
Get Kernel StatusTool to get the status of a Kaggle kernel run.
List Kaggle DatasetsTool to list Kaggle datasets with filters and pagination.

Conclusion

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

How to build Kaggle MCP Agent with another framework

FAQ

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

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

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

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