MCP server exposing the Vibedasher data engine (datasets, query, viz) to a customer's AI.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vibedasher-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# vibedasher-mcp An [MCP](https://modelcontextprotocol.io) server that exposes the **Vibedasher data engine** — datasets, CSV upload + ETL, headless SQL query, and dashboard (viz) management — as tools a customer's AI (Claude Code, Cursor, ...) can drive directly. This is the **control plane** (VD-601, PIVOT/PLAN.md EP-6). It wraps the published [`vibedasher` Python SDK](https://pypi.org/project/vibedasher/) and calls only the public, metered `/api/v1/*` API. **Install:** `pip install 'vibedasher-mcp>=0.6.0'`, then `vibedasher login` — no API key to mint. Live on PyPI since 2026-08-09, as are `vibedasher` (PyPI) and `@vibedasher/client` (npm). The **eject tools (VD-602) ship in this package**, not separately: `eject_viz`, `eject_viz_files`, `eject_instructions` and `get_viz_files` are registered by `register_eject_tools()` in `eject.py`. They pull a viz's code plus an SDK-wiring manifest so your AI can recreate the dashboard natively in your stack. ## Tools | Tool | What it does | |------|--------------| | `list_datasets` | List datasets the key can read (id, name, `cleanSQLName`, status). | | `get_dataset(dataset_id)` | One dataset's metadata + column schema. | | `upload_dataset(name, csv_content, ...)` | Create a CSV dataset, upload, load, poll to READY. | | `run_query(sql, dataset_ids, params, type)` | **Explore.** Inline alias-only SQL across your datasets (plural, joins allowed) → typed columns + rows in the response. `type="wasm"` returns a plan of presigned Parquet URLs instead of rows — the credential-free data lane for a standalone build, and the only call that builds a dataset's wasm extract. | | `run_query_to_file(sql, output_path, dataset_ids, params, format, overwrite)` | **Extract.** Same query, but the rows are written to a local CSV/JSONL file and never enter the response — you get back `path`, `rowCount`, `columns`, `bytes`, `truncated`. stdio only; absolute paths only; never clobbers without `overwrite=True`. | | `list_vizzes(include_unpubli…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.