TitanSigma

Attach a dataset to a report under a stable `key` (the built page passes it to loadData(key)). Provide EITHER `peaka_query_id` (a saved Peaka query — the deployed page executes it by id; prefer this when the user may want to materialize the query or put it on a refresh schedule later) OR a raw `sql` statement (the deployed page re-runs it directly). You may also pass `sql` alongside a query id to show a readable query in the app. The deployed dashboard always loads live data from Peaka by running the query, so no data rows are needed here. Re-attaching the same key replaces it.

attach_dataset

Create a TitanSigma project bound to an existing Peaka project. Get the Peaka project id/name from the Peaka MCP server (peaka_list_projects). Optionally pick the deploy subdomain (<subdomain>.<domain>); if omitted a unique one is derived from the name. Optionally pass org_id (from list_organizations) to create the project in a team — every member of that org will see it; omitted places it in your personal org.

create_project

Create a new (empty) report in a project.

create_report

Delete a TitanSigma project and all its reports, and tear down what it deployed: the live site and its Vercel project, the GitHub repo, and the project's Peaka deploy key. The Peaka project itself and its data connections are left untouched. Destructive and irreversible. If teardown fails, nothing is deleted and the error explains why.

delete_project

Delete a report. Destructive and irreversible.

delete_report

Deploy (publish) all of a project's built reports to its live site. The project must already have a Peaka deploy key provisioned (do a first Share in the TitanSigma web app once). Optionally pass `message` to set the git commit message for this deploy (e.g. what changed); when omitted, a deterministic filename-based message is used. Returns the URL and a commit sha to poll with get_deploy_status.

deploy_project

Check the live build state of a project's latest deploy. Pass the commit_sha from deploy_project; matched:false means Vercel hasn't registered that push yet — keep polling.

get_deploy_status

Get one TitanSigma project by its local id.

get_project

Get one report: its datasets (query keys, SQL, columns), whether it has a built page, and its live URL.

get_report

Check that the TitanSigma backend is reachable and healthy (MCP server up, your connection authorized, and the database responding). Use it to confirm your MCP connection and the service are working before building or deploying.

health_check