kaggle-mcp
Related Servers
Alternatives to kaggle-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides seamless integration with the Kaggle API, enabling interaction with competitions, datasets, kernels, and models through MCP-compatible clients.24 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceA full-featured MCP server with 96 tools for the Kaggle API, enabling users to manage competitions, datasets, notebooks, models, discussions, and workflows via natural language.MIT
- FlicenseBqualityDmaintenanceMCP server for Kaggle API integration that allows creating, running, and managing Kaggle notebooks programmatically.81-
- AlicenseBqualityCmaintenanceA local MCP server that exposes the SAIR Competition Public API as tools for MCP clients, enabling account introspection, competition browsing, submissions, playground operations, cheatsheet management, and Contributor Network interactions.48MIT
- AlicenseBqualityDmaintenanceMCP server for Codabench REST API that enables AI agents to drive a full participant ML-benchmark workflow: discover competitions, download data, submit, poll, and read leaderboards.16MIT
- FlicenseNot gradedqualityBmaintenanceZero-config MCP server that enables AI assistants to search and preview Kaggle datasets directly, with smart token trimming for efficient context usage.-
TDQS
Scored across 51 tools
Every tool has a clear resource prefix (competition_, dataset_, kernel_, model_, discussion_) followed by a distinct action verb. Overlaps are minimal and resolved by descriptions (e.g., dataset_download vs. dataset_download_file). The only minor issue is kernel_output's description being a copy-paste error, but tool names are unambiguous.
All tool names follow a consistent snake_case pattern of resource_prefix + action verb (e.g., competition_get, dataset_create, discussion_comments). No mixing of styles across the entire set.
With 51 tools, this is on the high side for a single MCP server. While each tool serves a specific purpose and the Kaggle API is broad, the number feels heavy, especially with 12+ discussion-related tools. It's borderline but still manageable for an agent.
The tool surface covers nearly all key Kaggle resources: competitions (list, get, submit, leaderboard, data), datasets (full CRUD, versions, downloads), kernels (push, pull, sessions), models (create, delete, instances, versions), discussions (search, list, comments), and file upload. Missing actions (e.g., delete submission/kernel) are minor and uncommon. Very comprehensive.