Kaggle MCP Server
Related Servers
Alternatives to Kaggle MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseNot gradedqualityBmaintenanceProvides a stdio MCP bridge for coding agents to query and record engineering knowledge locally, preserving debugging history, failed attempts, and verified solutions.2 npmMIT
- AlicenseAqualityBmaintenanceConnects a personal KodeKloud learning account to AI assistants such as Claude Desktop, Claude Code, Cursor, and ChatGPT, letting users review course progress and syllabi, inspect running hands-on labs, check certification exam readiness for CKA/CKAD/CKS/Terraform, track KodeKloud Engineer tasks, and generate weekly study plans through natural language. It runs read-only by default over stdio or remote SSE/streamable-HTTP transport, with session credentials auto-detected from a browser cookie or bearer token and redacted from all logs.9MIT

kadeep mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding agents such as Cursor and Claude Code to browse KaDeep projects, suites, test cases, runs, jobs and defects, run end-to-end tests, and check localization quality directly as tools. It exposes 14 tools over stdio so agents can answer questions like which smoke tests fail and why, or trigger the checkout tests themselves.1Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents to look up LeetCode public profiles, solved-problem counts by difficulty, recent accepted submissions, the daily coding challenge, and individual problem details by title slug through LeetCode's keyless GraphQL endpoint. Runs either as a local stdio server or via a hosted gateway URL, with no account required for initial calls.188 npmMIT
- AlicenseNot gradedqualityDmaintenanceA lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.2,323 npmMIT
TDQS
Scored across 51 tools
Multiple tools have overlapping purposes: discussions_trending, discussions_search, discussions_list, discussions_by_source, discussions_solutions, and discussions_writeups all retrieve discussion content with subtle differences; competition_leaderboard vs competition_leaderboard_download also confuse. Kernel_output's description mismatches its name, further muddying tool selection.
Names mostly follow snake_case with domain prefixes (competition_, dataset_, model_), but plural/singular inconsistency exists (discussions_* vs discussion_*; competitions_list vs competition_leaderboard). Some tool names are less predictable (kernel_output, file_upload), though the overall pattern remains readable.
51 tools is extreme over-provisioning for an MCP server and exceeds the 50+ threshold for severe mismatch. Even for Kaggle's broad surface, many tools could be consolidated (e.g., six discussion-listing variants), making the set unwieldy.
The server covers CRUD for datasets and models, plus competition submissions, kernel sessions, and discussion reading. Minor gaps exist (no update/delete for model instances, no discussion posting/reply), but core workflows are supported.