kaggle-mcp
Related Servers
Alternatives to kaggle-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables approved submission, monitoring, and retrieval of Kaggle CPU/GPU jobs, including two-stage preparation-to-training workflows, experiment comparison, artifact/log access, and SMTP completion notices.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to run and manage machine-learning training on Kaggle, Google Colab, and Hugging Face GPUs. Supports background runs, status and metrics, plots, checkpoints, Kaggle submissions, and Hugging Face Hub operations.54MIT
- AlicenseAqualityCmaintenanceEnables AI agents and their users to submit, route, and monitor training jobs across free-tier GPU clouds (Kaggle, Colab, Lightning, local MPS) through a local daemon that tracks quota, explains routing decisions, and gates long or secret-reading agent jobs behind human approval.81MIT
- AlicenseCqualityBmaintenanceA local stdio MCP server that lets agents submit and manage Python/notebook jobs on Kaggle and Google Colab, with quota-aware provider recommendation, job listing/reconciliation, downloads, and cancellation. It runs in a safe mock mode by default and requires double-gated flags before any real GPU or CCU-billed work is submitted.302Apache 2.0
- FlicenseBqualityCmaintenanceEnables running ML experiments from a local laptop by coordinating GitHub for code, Kaggle for data and GPU training, Weights & Biases for tracking runs, and Google Drive for small artifacts.14-
- AlicenseNot gradedqualityFmaintenanceEnables AI agents and CLI users to drive Kaggle notebooks end-to-end—pull, edit, save new versions, run, monitor, and fetch logs—using a local stdio MCP server with a Kaggle API token.MIT
TDQS
Scored across 9 tools
Each tool maps to a distinct action in the job or dataset lifecycle, and descriptions clarify the boundaries between look-alike pairs (job_status vs list_jobs, job_logs vs job_output). The only mild overlap is cleanup_job, which deletes a kernel plus its per-job dataset, versus delete_dataset for uploaded datasets — but the descriptions make that distinction explicit.
Eight of nine names follow a predictable snake_case verb_noun pattern (submit_job, list_jobs, upload_dataset, delete_dataset). The read-side tools (job_status, job_logs, job_output) drop the verb and lead with the noun, a minor but noticeable inconsistency in an otherwise clean scheme.
Nine tools is well scoped: six cover the remote job lifecycle and three cover reusable datasets, with no filler. Nothing looks redundant or missing from a count perspective.
The job lifecycle (submit, status, list, logs, output, cleanup) and dataset lifecycle (upload, list, delete) are both well covered. The notable gap is cancellation — job_status reports cancel_* states, yet there is no tool to cancel a running job, forcing reliance on time_limit_h.