ChatGPT Plugin

TitanSigma

Build and publish reports

Brand: Peaka

Category: Data & Analytics
Primary Subcategory: Self-Serve BI & Conversational Analytics

Integration details

Description

TitanSigma unifies all your data and sends it to your BI tool, simplifying how you track KPIs and metrics. No more digging through spreadsheets or chasing down reports. Just clear numbers your team can use to run the business better.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Data & Analytics
Primary Subcategory: Self-Serve BI & Conversational Analytics
Secondary Subcategories: None listed
Brand: Peaka
Access: Account required
First tracked: 2026-09-24
Tool count: 19
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Self-Serve BI & Conversational Analytics

View Category

Listed in alphabetical order

Primary Subcategory

ADECIComing soonGet notified

Adzviser Google AnalyticsComing soonGet notified

Adzviser ShopifyComing soonGet notified

AI for DatabaseComing soonGet notified

AI2SQLComing soonGet notified

TitanSigmaComing soonGet notified

Tools

19 tools agents can invoke

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. To rename an existing report, use rename_report instead — a new report gets a new URL and none of the old report's access rules.
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: its URL stops working and its access rules in the deployed /admin panel no longer apply. To rename a report, use rename_report instead.
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
List the organizations (teams) the caller belongs to — id, name, role, member count. Everyone in an org shares all its projects; pass an org's id as create_project's org_id to create a project in that team. Omitting org_id uses the caller's personal org.
list_organizations
List the caller's TitanSigma projects (workspaces) across all their organizations. Each project includes its org_id/org_name.
list_projects
List the reports in a project.
list_reports
Remove a dataset (query key) from a report.
remove_dataset
Rename a report. Only the display name changes: the report keeps its URL, so existing links keep working and its access rules in the deployed site's /admin panel are kept. Always use this to rename a report — never create a new report and delete the old one, which changes the URL and drops its access rules. The new name appears on the live site after the next deploy_project.
rename_report
Choose which identity provider end-viewers of the deployed site sign in with, and turn login on. provider "entra" = the customer's Microsoft Entra tenant — pass tenant_id and client_id from their SPA app registration (no client secret). Optionally pass admin_groups (a list of { id, name? } where id is an Entra security-group Object ID) to designate who may administer on-site report access via the deployed dashboard's /admin panel. provider "google" = sign in with Google via a shared TitanSigma app (no per-customer setup); pass allowed_domains (Google Workspace hosted domains like "peaka.com") and/or allowed_emails to restrict who can sign in — both empty means any Google account. For Google, optionally pass admin_emails to designate who may administer per-report access (by email/domain) via the deployed dashboard's /admin panel. provider "peaka" uses Peaka sign-in. This only changes settings — run deploy_project to publish.
set_project_auth
Toggle whether the deployed site requires viewers to sign in with Peaka. This only changes the setting — it does not affect the live site until the project is redeployed. If the project is already deployed, run deploy_project afterward to publish the change.
set_project_login
Set a project's deploy subdomain (its live site will be <subdomain>.<domain>). Allowed only before the project's first deploy.
set_project_subdomain
Set a report's page HTML (a complete single-page document). Read the titansigma://guide/report-page resource first — the page must call the injected loadData(key) for any dataset it shows.
set_report_page

FAQs

TitanSigma ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve TitanSigma's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are TitanSigma alternatives on ChatGPT?

As of 2026-11-02, TitanSigma competes with ADECI, Adzviser Google Analytics, Adzviser Shopify, AI for Database, AI2SQL, Alteryx Insights, AnalyticsLog, Anomaly AI and 81 more in ChatGPT Self-Serve BI & Conversational Analytics, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.