Kaggle MCP vs Stats Compass
A side-by-side look at the Kaggle MCP and Stats Compass MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kaggle MCP for data science tools work; choose Stats Compass for data science tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kaggle MCP when
- You need dedicated capabilities in the Data Science Tools domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
KAGGLE_USERNAME, KAGGLE_KEY. - You want tools like
dataset_ref, download_path.
Choose Stats Compass when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
STATS_COMPASS_PORT, STATS_COMPASS_SERVER_URL, STATS_COMPASS_MAX_UPLOAD_MB.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Science Tools | Data Science Tools |
| Quality signal | 47/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | KAGGLE_USERNAMEKAGGLE_KEY | STATS_COMPASS_PORTSTATS_COMPASS_SERVER_URLSTATS_COMPASS_MAX_UPLOAD_MB |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39 | 17 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Kaggle MCP | View Stats Compass |
Tools & capabilities
Kaggle MCP tools 2
dataset_refKaggle dataset reference in `owner/dataset-slug` format, for example `kaggle/titanic`.download_pathOptional local output path. If omitted, files are saved to `./datasets/<dataset_slug>/`.
Stats Compass tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kaggle MCP
No confirmed install command for Kaggle MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Stats Compass
{
"mcpServers": {
"stats-compass": {
"command": "uvx",
"args": [
"stats-compass-mcp"
],
"env": {
"STATS_COMPASS_PORT": "YOUR_STATS_COMPASS_PORT_HERE",
"STATS_COMPASS_SERVER_URL": "YOUR_STATS_COMPASS_SERVER_URL_HERE",
"STATS_COMPASS_MAX_UPLOAD_MB": "YOUR_STATS_COMPASS_MAX_UPLOAD_MB_HERE"
}
}
}
}
Frequently asked questions
Kaggle MCP is categorized under Data Science Tools and uses an install path we have not confirmed yet. Stats Compass belongs to Data Science Tools and uses a local stdio subprocess. Pick Kaggle MCP for data science tools work and Stats Compass for data science tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Kaggle MCP has no confirmed install command yet — follow its own setup instructions.
Kaggle MCP is listed as free. Auth: api key required. Stats Compass is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add arrismo-kaggle-mcp and stats-compass as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kaggle MCP has a quality signal of 47/100 (Fair) with 5 views, 0 installs and 39 GitHub stars. Stats Compass has 44/100 (Fair) with 3 views, 0 installs and 17 GitHub stars.