How to integrate Kaggle MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Kaggle logo
OpenCode logo
divider

How to integrate Kaggle MCP with OpenCode

This guide explains how to connect Kaggle MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Kaggle with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Kaggle with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Kaggle

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Kaggle Composio".
  3. Complete the authentication and authorization flow, and your Kaggle integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Kaggle to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Kaggle with OpenCode

Now, in the chat, ask the agent to connect to Kaggle or give it any Kaggle-related task.

For example, ask it to:

  • "Download data files for the Titanic competition"
  • "Create a new version of your COVID-19 dataset"
  • "Check processing status of your uploaded dataset"

It will prompt you to authenticate and authorize access to Kaggle.

That is it. Composio tools are now available in OpenCode, and your Kaggle account is ready to use.

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.

Way Forward

Now that Kaggle is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

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 OpenCode?

Yes, you can. OpenCode 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.