Scaffold the project and settle the Kaggle CLI/MCP design #1

Closed
opened 2026-11-11 21:58:08 +00:00 by dsh · 2 comments
Owner

Context

New project dsh-kaggle: agent-native Kaggle tools for DSH, distilled from the CLI workflows in ml-lab/LinA, ml-lab/tardits and ml-lab/hijack. Kaggle now ships both a CLI and an official MCP server (beta); we want first-class tools, not shell incantations.

Bootcamp: https://git.pvlb.dev/ops/srvbtw/wiki/DSH-Bootcamp

Done in this issue

  • Bootcamp read; house layout in place (AGENTS.md map, ignored GIT.md, input box, four Forgejo workflows, labels).
  • Recon: DSH 0.2.2-rc.1; Kaggle MCP https://www.kaggle.com/mcp advertises 76 tools unauthenticated.
  • Research Kaggle CLI surface -> docs/kaggle-cli.md.
  • Research Kaggle MCP surface + auth -> docs/kaggle-mcp.md.
  • Design: CLI-vs-MCP coverage, tool names/contracts, safety invariants -> docs/design.md + docs/roadmap.md.
  • Decide: CLI wrapper only, or CLI-first + native API for read paths (no Python dependency).

Acceptance

  • docs/design.md lists every planned kaggle_* tool with parameters, return shape, safety rules and the CLI command (or MCP tool) behind it.
  • The design says explicitly which capability is served by the CLI, which by MCP, and which is out of scope.
  • Follow-up issues created for implementation slices, labeled type/task + area/dsh + priority/*.
## Context New project `dsh-kaggle`: agent-native Kaggle tools for DSH, distilled from the CLI workflows in `ml-lab/LinA`, `ml-lab/tardits` and `ml-lab/hijack`. Kaggle now ships both a CLI and an official MCP server (beta); we want first-class tools, not shell incantations. Bootcamp: https://git.pvlb.dev/ops/srvbtw/wiki/DSH-Bootcamp ## Done in this issue - [x] Bootcamp read; house layout in place (`AGENTS.md` map, ignored `GIT.md`, input box, four Forgejo workflows, labels). - [x] Recon: DSH 0.2.2-rc.1; Kaggle MCP `https://www.kaggle.com/mcp` advertises 76 tools unauthenticated. - [ ] Research Kaggle CLI surface -> `docs/kaggle-cli.md`. - [ ] Research Kaggle MCP surface + auth -> `docs/kaggle-mcp.md`. - [ ] Design: CLI-vs-MCP coverage, tool names/contracts, safety invariants -> `docs/design.md` + `docs/roadmap.md`. - [ ] Decide: CLI wrapper only, or CLI-first + native API for read paths (no Python dependency). ## Acceptance - `docs/design.md` lists every planned `kaggle_*` tool with parameters, return shape, safety rules and the CLI command (or MCP tool) behind it. - The design says explicitly which capability is served by the CLI, which by MCP, and which is out of scope. - Follow-up issues created for implementation slices, labeled `type/task` + `area/dsh` + `priority/*`.
Author
Owner

0.1.0 implemented and pushed (89bd8b4)

  • 31 native tools over Kaggle CLI 2.2.x + 2 MCP diagnostics; optional MCP adapter (off by default).
  • 60 offline tests (npm run check) against a fake CLI; npm pack --dry-run clean.
  • Research + design landed: docs/kaggle-cli.md, docs/kaggle-mcp.md, docs/design.md, docs/roadmap.md, docs/releasing.md.
  • Follow-ups: #2 (live smoke, needs operator credential), #3 (MCP flattening + benchmarks).

Verification

  • Offline only: no Kaggle credential on this box, so no live call. MCP is fake-client tested.
  • Install into the web profile is blocked: the profile's plugin-manager config still points at /opt/node-v24.22.0-linux-x64/bin/pnpm, which does not exist on srvbtw (pnpm lives at /usr/bin/pnpm). plugin_manager install_bundle fails with ENOENT before touching the package. Awaiting an operator decision on fixing that one line (profile change, outside this repo).

CLI vs MCP coverage (short)

  • CLI owns: local download/unzip/resume, upload folder prep, OAuth login, competition hosting, notebook push/pull, models, forums, quota.
  • MCP adds: interactive notebook sessions, benchmarks, write-ups/resolved links, simulation episodes; public search/topics work anonymously, account tools need a KGAT bearer token.
  • MCP downloads are signed URLs/file objects, not local files — real downloads stay on the CLI.
## 0.1.0 implemented and pushed (`89bd8b4`) - 31 native tools over Kaggle CLI 2.2.x + 2 MCP diagnostics; optional MCP adapter (off by default). - 60 offline tests (`npm run check`) against a fake CLI; `npm pack --dry-run` clean. - Research + design landed: `docs/kaggle-cli.md`, `docs/kaggle-mcp.md`, `docs/design.md`, `docs/roadmap.md`, `docs/releasing.md`. - Follow-ups: #2 (live smoke, needs operator credential), #3 (MCP flattening + benchmarks). ### Verification - Offline only: no Kaggle credential on this box, so no live call. MCP is fake-client tested. - **Install into the `web` profile is blocked**: the profile's plugin-manager config still points at `/opt/node-v24.22.0-linux-x64/bin/pnpm`, which does not exist on srvbtw (pnpm lives at `/usr/bin/pnpm`). `plugin_manager install_bundle` fails with ENOENT before touching the package. Awaiting an operator decision on fixing that one line (profile change, outside this repo). ### CLI vs MCP coverage (short) - CLI owns: local download/unzip/resume, upload folder prep, OAuth login, competition hosting, notebook push/pull, models, forums, quota. - MCP adds: interactive notebook sessions, benchmarks, write-ups/resolved links, simulation episodes; public search/topics work anonymously, account tools need a KGAT bearer token. - MCP downloads are signed URLs/file objects, not local files — real downloads stay on the CLI.
Author
Owner

Closed — 0.1.0 shipped

  • Design + implementation landed; 61 offline tests, CI green on master (#772, #773).
  • Installed live in the web profile after fixing the stale pnpmCommand (ops/srvbtw#48); 33 tools registered. kaggle_plugin_info and kaggle_datasets_list were exercised in-session (the latter correctly returns cli_missing because the Kaggle CLI is not in the Host PATH).
  • v0.1.0 tagged signed at 5236f85; Forgejo release page created; npmjs job skipped (no NPMJS_TOKEN).
  • Remaining, operator-only: registry publish needs the AUDIENCE repo variable or NPM_TOKEN → #4. Live Kaggle verification needs a credential → #2. MCP flattening/benchmarks → #3.

Nothing else is blocked on agent work in this issue.

## Closed — 0.1.0 shipped - Design + implementation landed; 61 offline tests, CI green on `master` (#772, #773). - Installed live in the `web` profile after fixing the stale `pnpmCommand` (ops/srvbtw#48); 33 tools registered. `kaggle_plugin_info` and `kaggle_datasets_list` were exercised in-session (the latter correctly returns `cli_missing` because the Kaggle CLI is not in the Host PATH). - `v0.1.0` tagged signed at `5236f85`; Forgejo release page created; npmjs job skipped (no `NPMJS_TOKEN`). - Remaining, operator-only: registry publish needs the `AUDIENCE` repo variable or `NPM_TOKEN` → #4. Live Kaggle verification needs a credential → #2. MCP flattening/benchmarks → #3. Nothing else is blocked on agent work in this issue.
dsh closed this issue 2026-11-11 22:16:50 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dsh-plugins/dsh-kaggle#1
No description provided.