Ziga Potocnik

Most data work isn t analysis. It s setup and upkeep.

Creating a data source for a new client. Pushing rows from an internal tool. Building the same custom metric for the fifth account in a row. Checking why last night s ingestion failed. Updating permissions when someone leaves the team.

All of it lives behind clicks. So it doesn t run in CI, it doesn t run on a schedule, and your AI agent can t touch it.

That s why we built Databox CLI - launching on Product Hunt on November 6. It puts the Databox API in your terminal: data sources, datasets, data ingestion, custom metrics, databoards, users and client accounts. One install, JSON or CSV output, clear exit codes for scripts. It also ships with agent skills, so Claude Code (or any agent that runs shell commands) can manage your Databox setup for you.

Yesterday (September 28th), we launched MCP Connectors by Databox, and you pushed it all the way to #1 Product of the Day. It's our first #1, and we couldn't have done it without you.

Huge thanks to the Databox team and to everyone here who upvoted, commented, asked the hard questions, and connected their first tool. You helped us confirm something we'd suspected for a while: knowing that a number moved isn't enough. People want to know why.

A few things we heard loud and clear:

https://www.producthunt.com/prod...

Last week I asked here where you go to find out why a number moved. The answers were almost all the same: the CRM, Slack, the support desk, Linear, a doc somewhere. Anywhere except the dashboard.

That's what we launched today.

With MCP Connectors, you connect the tools your team already uses, and Genie, our AI Analyst, uses them to answer your questions. Ask why signups dropped 18%, and it checks Linear, finds the signup form that shipped Tuesday and breaks on Safari, and ties it to the drop. You get the number and the reason in one answer.