Safe Kaggle MCP vs Next Devtools MCP
A side-by-side look at the Safe Kaggle MCP and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Safe Kaggle MCP for data science tools work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Safe Kaggle MCP when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
kaggle_whoami, kaggle_status, kaggle_audit_log.
Choose Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Science Tools | Developer Tools |
| Quality signal | 53/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 832 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 41 | 4 |
| Full listing | View Safe Kaggle MCP | View Next Devtools MCP |
Tools & capabilities
Safe Kaggle MCP tools 41
kaggle_whoamiReturn the authenticated Kaggle username and credential source. Does not transmit or echo the API key. Use to confirm the server resolved credentials for the expected account.kaggle_statusHealth check: credential validity, current per-competition submission budgets for this session, enabled safety switches, and the work-dir root.kaggle_audit_logReturn the session's append-only ledger of mutating actions (submit / create / version / delete) with timestamps and the submission budget at the time — every field redacted. Makes the safety machinery inspectable, which no other Kaggle MCP can offer (none track tokens or budgets).kaggle_list_competitionsList/triage competitions as a compact ranked table (title, slug, prize, deadline, evaluation metric, category). Paginated. Read-only.kaggle_competition_landscapePre-digested triage report of competitions: for each, the slug, prize, evaluation metric, deadline, and **days_left** — sorted by soonest deadline so you can decide what to enter at a glance. A single decision-ready artifact rather than raw endpoint output (which is what other Kaggle MCPs return).kaggle_get_competitionFetch one competition's details and a truncated, untrusted-wrapped rules digest. `competition` is the BARE slug (e.g. 'titanic'). Read-only.kaggle_competition_leaderboardPublic leaderboard capped to top-N (default 20) to protect context.kaggle_leaderboard_trackSnapshot the public top-N and diff it against the LAST snapshot you took: per-team rank deltas, new entrants, biggest climbers, and (if your_team is given) your movement + who passed you. Kaggle has no historical-leaderboard endpoint, so this stateful local tracking is unique. PUBLIC leaderboard only; deltas are vs your previous snapshot, not an absolute time series.kaggle_download_competition_filesDownload competition data into an isolated work dir (zip auto-extracted with a zip-slip guard). Returns local paths + metadata, NOT file contents. Requires the competition's rules accepted (403 otherwise).kaggle_eda_competitionDownload a competition's data and return a pre-first-submission view: a compact pandas digest per CSV (shape/dtypes/missingness/correlations) PLUS a train-vs-test column diff that auto-infers the target — the orientation no other Kaggle MCP ships. Requires the competition rules accepted (403 else).kaggle_competition_kickoffOne-call competition kickoff: fetch the metric/deadline/rules, download the data if rules are accepted (otherwise tell you to accept first), run a train/test EDA with target auto-detection, and return a baseline plan plus your remaining submission budget. Collapses the manual setup ritual into a single decision-ready bundle — no other Kaggle MCP does this.kaggle_submission_best_scoreReduce raw submission history to the decision signal: best public score (respecting metric direction), first/best/latest trend, today's submission count, and any failure reasons — the 'is it worth iterating?' answer other servers leave as a raw list. Public scores only (private score is hidden until the deadline).- +29 more on the listing page
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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.
Safe Kaggle MCP
{
"mcpServers": {
"safe-kaggle-mcp": {
"command": "uvx",
"args": [
"--from",
"safe-kaggle-mcp",
"kaggle-mcp"
]
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Safe Kaggle MCP is categorized under Data Science Tools and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Safe Kaggle MCP for data science tools work and Next Devtools MCP for developer 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.
Safe Kaggle MCP has no declared pricing — check the project's own site. Next Devtools MCP 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 safe-kaggle-mcp and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Safe Kaggle MCP has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.