Ai Viral
Paid
Indie SaaS founders shipping with tools like Lovable or Cursor
The AI returns 92,118 fans; the right answer is 71,204 — because nobody told it which accounts to exclude. Setoku is a self-hosted MCP knowledge server built to close that gap: it forces the AI to read what your data means before it touches a single row.
The server provides read-only query access to your data alongside a persistent, human-curated layer of metric definitions and known gotchas — so when the AI asks for merchandise revenue and the data is incomplete, it flags the gap rather than returning a wrong total. Proposed changes to that knowledge layer require a person to approve them in the admin console, so a bad session cannot silently rewrite your definitions. Published dashboards run on live data at a static link, with no frontend to maintain. The ceiling appears when your data questions require joins or transformations the analytics engine cannot express, at which point you are writing custom integrations via the connect skill.
Bottom line: Pick this for a team that keeps correcting the same AI query mistakes because nobody encoded the business rules; skip it if your reporting layer already enforces metric definitions centrally and you need something the whole org can self-serve without a self-hosted box to run.
Find your fit
More options in Business. Compare pricing, platforms, and features side by side.
Paid
Indie SaaS founders shipping with tools like Lovable or Cursor
Freemium
Marketing teams running social ad campaigns
Setoku runs as a self-hosted MCP server that gives any MCP-compatible AI client — Claude, Codex, or similar — read-only access to your structured data plus a queryable knowledge layer describing what that data means. The core loop: the AI calls find_context or get_metric before running a query, reads the canonical definition and any recorded gotchas, then executes against a read-only analytics mirror. Row caps, statement timeouts, and an append-only audit log are enforced at the database engine level, not by parsing SQL after the fact. Claude Code skills handle setup: /setoku:onboard wires a repo, /setoku:connect adds a data source, /setoku:generate drafts business context from existing code, and /setoku:curate queues knowledge changes for a human to accept.
The differentiating feature is the correction loop. When the AI encounters a definition it doesn’t have, it can propose an update — but that proposal sits in the admin page until a person approves it, outside any agent execution path. Nothing an injected or runaway session does can silently alter the knowledge base. The vendor explicitly notes this design choice as a guard against prompt injection rewriting the system’s understanding of your metrics.
Publishing works through two MCP tools: publish_app and update_app turn a query result or dashboard into a live-data web app at a shareable link, with no deployment step and no frontend code to maintain. The demo shows this with a sponsorship pricing table and an attendance forecast, both wired to live demo data. The model does no inference on the server, so adding Setoku does not increase inference costs — it connects to whatever AI you are already running.
The self-hosted requirement is the practical constraint most teams hit first. There is no hosted option described anywhere in the documentation or vendor page; you run this on your own VPS or internal infrastructure. Each user gets a revocable token embedded in their connector URL. The Apache-2.0 license means the code is auditable and forkable, which matters for teams with strict data residency requirements — but it also means support is community-driven, not contractual.
Sign in to rate this tool or suggest an edit.