Kaggle NodeJS MCP Server

Created By
goeffthomasa year ago
Overview

what is Kaggle NodeJS MCP Server?

Kaggle NodeJS MCP Server is a tool that allows users to explore Kaggle datasets and create notebooks using them through a Node.js environment.

how to use Kaggle NodeJS MCP Server?

To use this server, download the repository, add your KAGGLE_USERNAME and KAGGLE_KEY to a .env file at the root of the repo, run npm run build, and connect to an MCP client.

key features of Kaggle NodeJS MCP Server?

  • Easy access to Kaggle datasets
  • Integration with Node.js for data manipulation
  • Ability to create and manage notebooks

use cases of Kaggle NodeJS MCP Server?

  1. Data analysis and visualization using Kaggle datasets.
  2. Building machine learning models with data sourced from Kaggle.
  3. Collaborative data science projects using notebooks.

FAQ from Kaggle NodeJS MCP Server?

  • What do I need to run this server?

You need Node.js installed and a valid Kaggle account with API credentials.

  • Is there any cost associated with using Kaggle datasets?

No, accessing Kaggle datasets is free, but you need to comply with the dataset's licensing terms.

  • Can I use this server for production applications?

This server is primarily for development and exploration; for production, consider using more robust solutions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
goeffthomas
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago