mcp-server-kaggle-exec
MCP server that executes Python code on Kaggle GPU runtimes (T4 x2, P100, TPU) from any MCP-compatible AI assistant — Claude Code, Claude Desktop, Gemini CLI, Cline, and others. Run GPU-accelerated code (CUDA, PyTorch, TensorFlow) without local GPU hardware using Kaggle's free 30hr/week GPU quota.
Prerequisites
- Python 3.10+
- A Kaggle account
- Kaggle API credentials: either
KAGGLE_API_TOKENenv var (KGAT_* token) or~/.kaggle/kaggle.json(see Authentication)
Installation
pip install mcp-server-kaggle-exec
Or run directly with uvx:
uvx mcp-server-kaggle-exec
Configuration
Claude Code
Add to your project's .mcp.json or ~/.claude/.mcp.json:
{
"mcpServers": {
"kaggle-exec": {
"command": "mcp-server-kaggle-exec"
}
}
}
Or via the CLI:
claude mcp add kaggle-exec mcp-server-kaggle-exec
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"kaggle-exec": {
"command": "mcp-server-kaggle-exec"
}
}
}
Gemini CLI
gemini mcp add kaggle-exec -- mcp-server-kaggle-exec
Tools
kaggle_execute
Execute inline Python code on a Kaggle GPU kernel.
| Parameter | Type | Default | Description |
|---|---|---|---|
code |
string | — | Python code to execute (required) |
enable_gpu |
bool | true |
Whether to request GPU acceleration |
timeout |
int | 600 |
Max wait time in seconds |
Returns JSON with stdout, stderr, status, output_files, and execution_time.
kaggle_execute_file
Execute a local .py file on a Kaggle GPU kernel.
| Parameter | Type | Default | Description |
|---|---|---|---|
file_path |
string | — | Path to a local .py file (required) |
enable_gpu |
bool | true |
Whether to request GPU acceleration |
timeout |
int | 600 |
Max wait time in seconds |
kaggle_execute_notebook
Execute code and download all generated output files (images, models, CSVs, etc.).
| Parameter | Type | Default | Description |
|---|---|---|---|
code |
string | — | Python code to execute (required) |
output_dir |
string | — | Local directory for downloaded artifacts (required) |
enable_gpu |
bool | true |
Whether to request GPU acceleration |
timeout |
int | 600 |
Max wait time in seconds |
Output files are downloaded to output_dir. To save files for download, write them to the current directory in your Kaggle code.
Examples
Check GPU availability:
kaggle_execute(code="import torch; print(torch.cuda.is_available()); print(torch.cuda.get_device_name(0))")
Run nvidia-smi:
kaggle_execute(code="import subprocess; print(subprocess.run(['nvidia-smi'], capture_output=True, text=True).stdout)")
Train a model and download weights:
kaggle_execute_notebook(
code="import torch; model = torch.nn.Linear(10, 1); torch.save(model.state_dict(), 'model.pt')",
output_dir="./outputs"
)
CPU-only execution (faster startup):
kaggle_execute(code="print('Hello from Kaggle!')", enable_gpu=False)
How It Works
Unlike Google Colab (which uses real-time WebSocket execution), Kaggle uses batch execution:
- Your code is pushed as a private Kaggle kernel
- Kaggle queues and runs the kernel (30-120s startup + execution time)
- Once complete, the output log and files are downloaded
- The kernel is cleaned up (left as private)
This means there's no streaming output — you get results only after execution completes.
Authentication
Two authentication methods are supported:
Option 1: KGAT_* Access Token (recommended)
Kaggle API v2 access tokens (KGAT_* format) work via environment variable:
export KAGGLE_API_TOKEN=KGAT_your_token_here
To get a token: go to kaggle.com/settings → API → Create New Access Token.
When using with MCP, pass the env var in your server config:
{
"mcpServers": {
"kaggle-exec": {
"command": "mcp-server-kaggle-exec",
"env": {
"KAGGLE_API_TOKEN": "KGAT_your_token_here"
}
}
}
}
Option 2: Legacy kaggle.json
Place your Kaggle API key at ~/.kaggle/kaggle.json:
- Go to kaggle.com/settings
- Scroll to API section
- Click Create New Token
- Move the downloaded
kaggle.jsonto~/.kaggle/kaggle.json - Set permissions:
chmod 600 ~/.kaggle/kaggle.json
GPU Quota
Kaggle provides ~30 hours of free GPU per week. The API supports enable_gpu: true/false but does not allow selecting specific GPU types (T4 vs P100) — Kaggle assigns the GPU automatically.
For CPU-only tasks, set enable_gpu=False to avoid consuming GPU quota.
Troubleshooting
"Kaggle authentication failed" — Ensure either KAGGLE_API_TOKEN env var is set (KGAT_* token) or ~/.kaggle/kaggle.json exists. See Authentication above.
"Kernel timed out" — Increase the timeout parameter. Kaggle kernel startup can take 30-120 seconds, plus execution time.
"GPU quota exceeded" — You've used your ~30hr weekly GPU quota. Wait for the weekly reset or use enable_gpu=False for CPU-only execution.
"Kernel status: error" — Check the stderr in the response for Python errors in your code.
Comparison with mcp-server-colab-exec
| Aspect | colab-exec | kaggle-exec |
|---|---|---|
| Execution model | Real-time (WebSocket) | Batch (push + poll) |
| Startup time | ~10-30s | ~30-120s |
| Auth | Google OAuth2 (browser) | API token file |
| GPU types | T4, L4 | T4 x2, P100, TPU |
| GPU selection | Can pick T4/L4 | API only supports on/off |
| Free quota | Usage-based | ~30 hr/week |
| Output | Streaming | After completion |
License
MIT
Metadata
Release files for mcp-server-kaggle-exec 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_server_kaggle_exec-0.1.0.tar.gz | 15.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_kaggle_exec-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.4 kB
Release files / mcp_server_kaggle_exec-0.1.0.tar.gz
| Download URL | mcp_server_kaggle_exec-0.1.0.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9dd9d836b5b3c8f11e4fa0b31fd84029abf9b0d630281cacb51d239e076d35f9
|
|
BLAKE2b-256 checksum How to use checksums |
90014738916b8ab3f659b8da1ffbc2208ea097b1bac15b4a9b563900b2e8f463
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 15, 2026.
Transparency logRelease files / mcp_server_kaggle_exec-0.1.0-py3-none-any.whl
| Download URL | mcp_server_kaggle_exec-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
decb3ac41edade22e711f3fe0b7e8a6640be19b484717f1155ae8909c6c84947
|
|
BLAKE2b-256 checksum How to use checksums |
bcdd75eaa4266d5f225e7a28f42048bc2d41ab717a9615ebdaf48aca7e03ce19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 15, 2026.
Transparency logSecurity for mcp-server-kaggle-exec 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_server_kaggle_exec-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.