Do I need an account to use these tools?
Yes for any surface that touches your data: MCP, Shell CLI, and Chat all require a DataUnmess workspace. The Chat surface uses your browser session; MCP and the Shell CLI use a workspace-scoped key issued from your account settings.
Where does the MCP server actually run?
Hosted at https://app.dataunmess.ai/api/mcp (the MCP route lives inside the same Next.js app on Railway — separate subdomain not needed). For local dev, run `pnpm dev:mcp` and point your AI client at http://localhost:3100/mcp.
Why is remove_chart chat-only?
Destructive operations (remove_chart, remove_flowchart) need conversational context to confirm intent before deleting. The web chat can ask 'are you sure?' and remember the answer; external MCP clients cannot reliably do that. We exclude these from MCP rather than risk an AI deleting work without confirmation.
Can I use my existing Claude / Gemini / ChatGPT subscription?
Yes. Add our hosted MCP endpoint plus a workspace-scoped MCP key to Codex Desktop, Claude Code, Gemini, Claude Desktop, Cursor, Windsurf, ChatGPT, or any MCP-compatible client. Their AI then drives DataUnmess tools using tokens from your subscription. No in-app AI tokens consumed. See the Connect your AI page for setup steps.
When should I use the shell CLI instead of MCP?
Use the shell CLI for scheduled jobs, CI pipelines, and scripts where you don't want an AI in the loop. The CLI is deterministic — same command, same output. MCP is for humans collaborating with an AI; the CLI is for machines following a script.
Some tools show 'gap' — what does that mean?
A gap is a tool we plan to support on that surface but haven't shipped yet. Gaps are tracked in TOOL_PARITY.md and addressed in priority order. Raw dataset upload is intentionally not an AI/MCP tool; use the web UI or `dash-ai datasets upload <file>` for local files, and use Data Pipelines for connected-source imports.