Safe Kaggle MCP Server

Safe Kaggle MCP is an MCP integration. Safety-first Kaggle MCP — confirm-gated destructive ops, submission budget, injection-fenced.

Packages and local setup

The published pypi package is safe-kaggle-mcp, version 0.4.1. Its declared MCP transport is stdio.

The package declares KAGGLE_USERNAME: Kaggle account username (legacy scheme; pair with KAGGLE_KEY). Optional — read-only tools work without credentials.; KAGGLE_KEY: Kaggle API key, the 40-char 'key' from kaggle.json (legacy scheme; pair with KAGGLE_USERNAME).; KAGGLE_API_TOKEN: Modern Kaggle KGAT_... token (alternative to KAGGLE_USERNAME/KAGGLE_KEY). Optional.; KAGGLE_MCP_ENABLE_DESTRUCTIVE: Set to 1 to expose delete tools. Default 0 (off).; KAGGLE_MCP_ENABLE_PUBLISH: Set to 1 to allow making datasets/kernels public. Default 0 (off).; KAGGLE_MCP_SUBMISSION_CAP: Daily per-competition submission budget. Default 5..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.4.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.