Skip to main content
Glama
Kaggle MCP Server

Kaggle MCP Server

by Dishant27

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KAGGLE_KEYNoYour Kaggle API key. Required if not using kaggle.json.
KAGGLE_USERNAMENoYour Kaggle username. Required if not using kaggle.json.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list-competitionsD–
download-competitionD–
submit-to-competitionD–
list-submissionsD–

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.8/5.0

Scored across 4 tools

Disambiguation4/5

The four tools target distinct resources and actions: listing competitions, downloading a competition, submitting to a competition, and listing submissions. Without descriptions, some scope details are ambiguous, such as exactly what download-competition returns or whether list-submissions is competition-scoped or user-scoped.

Naming Consistency4/5

All names use kebab-case and generally follow a verb-object pattern: list-competitions, download-competition, list-submissions. submit-to-competition is slightly less consistent because it inserts a preposition, but the overall convention is still predictable.

Tool Count4/5

Four tools is a compact but reasonable surface for a competition-focused Kaggle server. It may be slightly thin, but each tool has a clear role in the basic competition workflow.

Completeness3/5

The surface covers listing competitions, downloading competition data, submitting, and listing submissions, but notable competition operations are missing, such as getting competition details, viewing leaderboards, or listing competition files. These gaps would limit an agent's ability to fully navigate Kaggle competitions.