What's going on?
Health of your data sources, the metrics that matter, and how many approvals are waiting.
Anything I need to approve?
One unified queue of everything waiting on your decision, oldest first.
Walk me through my app
A grounded tour: what’s connected, what’s live, where revenue comes from, what’s gated.
The connector is read-only today. It can read your workspace and tell you what’s
waiting — it can never approve, launch, change, or spend anything. You approve in
the dashboard. A guarded write path (
decide_approval) is planned as a separate,
opt-in scope.What the assistant can do
Under the hood the connector exposes four tools and three one-click prompts. You don’t call these by name — the assistant picks the right one from your question — but this is exactly what it can reach:| Tool | Answers | Returns |
|---|---|---|
get_status | ”What’s going on?”, “How are things?” | Source health, KPIs (MRR, active subs, trials, CAC, ROAS — with honest unavailable where data is missing), readiness state, count of waiting approvals |
list_pending_approvals | ”Anything I need to approve?”, “What’s waiting on me?” | The unified queue across campaign launches, growth actions, growth-memory drafts, and onboarding go-lives — oldest first, each with a stable id |
get_approval | ”Tell me about that campaign approval” | Full detail for one item: what changes if approved, who requested it, the artifact version a decision pins |
explain | ”Walk me through my app”, “Explain my setup” | A grounded tour built from your overview, integration health, and growth profile. Optional focus: integrations, revenue, growth, campaigns, onboarding |
daily_briefing,
whats_waiting_on_me, show_me_around.
Example prompts
What it can’t do
- Approve, launch, edit, or spend. Read-only. It surfaces what’s waiting and points you to the dashboard to decide.
- Reach raw ad accounts, payment systems, or the warehouse. It only sees the same summarized, tenant-scoped reads the dashboard serves.
- See another company’s data. Your workspace is fixed to the connection’s sign-in — it can’t be widened by anything you type.
Security & privacy
Scoped to you
Your
companyId comes from the token you signed in with — never from a prompt. No request can point the connector at another tenant.Read-only by scope
Connections are granted
status:read. There is no write scope to grant yet, so nothing the assistant reads can trigger an action.Audited
Reads and (later) writes are attributable to you. Any future approval from chat is recorded in the same hash-chained audit log as the dashboard.
Revocable
Every connection shows up in Settings → Connected assistants. Revoke one and it stops working immediately.
Which assistants work
Both Claude and ChatGPT connect to the same server — it speaks standard MCP, so there’s nothing vendor-specific to configure.| Client | How it connects | Guide |
|---|---|---|
| Claude.ai (Pro/Team/Enterprise custom connectors) | OAuth sign-in | Connect from Claude |
| Claude Code (CLI) | Bearer token | Connect from Claude |
| ChatGPT (Developer Mode connectors) | OAuth sign-in | Connect from ChatGPT |
| OpenAI API (Responses / Agents SDK) | Bearer token | Connect from ChatGPT |
Server URL
https://api.dashboard.flokitai.com/mcpConnect from Claude
claude.ai custom connector or the Claude Code CLI.
Connect from ChatGPT
ChatGPT Developer Mode or the OpenAI API.