kaggle-mcp MCP server
A MCP server for Kaggle Apis
Components
Tools
The server implements one tool:
- add-note: Adds a new note to the server
- Takes "name" and "content" as required string arguments
- Updates server state and notifies clients of resource changes
Configuration
Ensure that you have downloaded your Kaggle credentials
(kaggle.json) and placed it in the ~/.kaggle/ directory (this is the default
location where the Kaggle API looks for your credentials)
Otherwise you can add the env KAGGLE_USERNAME and KAGGLE_KEY to the mcp config
Quickstart
Install
Claude Desktop
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Development/Unpublished Servers Configuration
``` "mcpServers": { "kaggle-mcp": { "command": "uv", "args": [ "--directory", "/Users/{username}/Work/kaggle-mcp", "run", "kaggle-mcp" ] } } ```Published Servers Configuration
``` "mcpServers": { "kaggle-mcp": { "command": "uvx", "args": [ "kaggle-mcp" ] } } ```Development
Building and Publishing
To prepare the package for distribution:
- Sync dependencies and update lockfile:
uv sync
- Build package distributions:
uv build
This will create source and wheel distributions in the dist/ directory.
- Publish to PyPI:
uv publish
Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token:
--tokenorUV_PUBLISH_TOKEN - Or username/password:
--username/UV_PUBLISH_USERNAMEand--password/UV_PUBLISH_PASSWORD
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory /Users/{username}/Work/kaggle-mcp run kaggle-mcp
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
1 maintainer
Metadata
1 maintainer
Release files for kaggle-mcp 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 | |
|---|---|---|---|---|
| kaggle_mcp-0.1.0.tar.gz | 64.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kaggle_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.7 kB
Release files / kaggle_mcp-0.1.0.tar.gz
| Download URL | kaggle_mcp-0.1.0.tar.gz |
|---|---|
| Size | 64.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce3b834f1c86a21df5f143aa9bc5b5d57711a458395eef6828cdaf2334b06b1e
|
|
BLAKE2b-256 checksum How to use checksums |
d42e579adcea95faed6ae830c50bd22ca55ef2a23b8e8f2279d5060513ad85a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.6
|
Release files / kaggle_mcp-0.1.0-py3-none-any.whl
| Download URL | kaggle_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
738012172f6177e43d6910cf87760b913397d09e8e0c50e7df14d526a09cf3a4
|
|
BLAKE2b-256 checksum How to use checksums |
45ab8a362e67db61cd68f3a89712a72e6db3ebb18d558942763a082ecdcf390b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.6
|
Security for kaggle-mcp 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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
