MCP Tool Reference
The FunnelFizz MCP server exposes around 120 tools organized into dot-prefixed namespaces so your agent can scan one prefix at a time. This page is the namespace-level index. The full per-tool signatures and examples are auto-generated from the server's tool definitions; for the canonical write surface and walkthroughs see Mutations & writes.
Namespaces
| Namespace | What it covers |
|---|---|
workspace.* | Workspace profile, brand, onboarding state, custom event registry, transfer/delete. |
funnel.* | Funnel CRUD, stages, tracks, splits, extensions, provider links, replay, drilldowns. |
email.* | Drafts, sends, drips, templates, senders, domains, assets, campaign analytics. |
automation.* | Automation drafts, steps, canvas, activate/pause/resume, runs, stats. |
team.* | List members and invites; invite, remove, change role (T2 admin). |
billing.* | Plans, subscription state, invoices, checkout/portal handoffs, cancel/resume/change (T2 admin). |
integration.* | Provider list, OAuth handoffs, configuration, disconnect; Stripe-specific subnamespace. |
tracking.* | Tracking site add/check/list/get_metrics/update/delete. |
report.* | List, get, generate AI reports; per-key quota. |
stage.* | Stage-level drilldowns (paths, sources, referrers, users, revenue, churn, mentions, ad/SEO envelopes). |
profile.* | Profile search and journey reads (PRO plan only). |
api_key.* | List keys, get activity, create, revoke (T2 admin). |
mcp.* | Change feed + revert primitives (list_changes, revert_change). |
Tier and scope quick reference
Every tool is gated by one of three safety tiers and one of four scopes. See Safety tiers for the full model.
| Tier | Gate | Examples |
|---|---|---|
| T0 | Plan + scope (filtered from tools/list if unavailable) | All *.list, *.get, *.get_metrics, drilldowns |
| T1 | Single-use 10-minute target token, minted after user confirms the entity | All structural writes: funnel/split/extension creation, email drafts/sends, automation activation, deletes |
| T2 | 6-digit code emailed to the API-key-holder, pasted back by user | team.* membership changes, billing.* plan changes, api_key.create/revoke, workspace.transfer_ownership, workspace.delete |
Per-tool detail
Full signatures, parameter schemas, and worked examples are generated from packages/mcp/src/tools/*.ts and are surfaced inside MCP clients via tools/list. For the write-side walkthroughs and the full T1 / T2 flow with code samples, see:
- Mutations & writes — every write tool with notes on tokens, fan-out, and reversibility.
- Safety tiers — the T0 / T1 / T2 model end-to-end.
- Admin actions — the T2 code-paste handshake.
- Browser handoffs — checkout, portal, OAuth flows.
- Revert changes —
mcp.list_changesandmcp.revert_change.
Related
- MCP overview — server URL, connection config, capability matrix.
- Setup with an agent — paste-prompt flow for new users.
- Reading docs —
llms.txt,llms-full.txt, Context7.