MCP resources and prompts
The reference the server carries — event vocabulary, playbook, kit guide, store guide — and the walkthrough prompts.
Resources — the documentation, in full
| Resource | What it contains |
|---|---|
| broctic://events/vocabulary | The exact event names, what each means, and the rules that keep them comparable. |
| broctic://events/http | The raw ingest contract, for a platform with no client. |
| broctic://sdk/swift | LEGACY: BrocticAnalytics.swift, in full — for an imported or hand-written Apple app. A Studio app is already instrumented by its kit. |
| broctic://sdk/typescript | LEGACY: broctic-analytics.ts, in full — for an imported or hand-written app. A Studio app is already instrumented by its kit. |
| broctic://playbook/checklist | Every onboarding, paywall, pricing and trial decision, with the metric it moves. |
| broctic://playbook/sources | Every figure with its publisher, year, sample and caveat. |
| broctic://playbook/all · broctic://playbook/{set} | The Studio playbook's requirements — all of them, or one rule set at a time. |
| broctic://kit/guide | The kit's components and the rules every screen follows (the same text as studio_kit_guide). |
| broctic://store/guide | How to take an app through App Store Connect with the store tools, in the order Apple accepts. |
| broctic://research/method | How the research opportunity score works, and what it does not mean — it ranks categories, it is not a download estimate. |
| broctic://guide/setup | How the pieces fit together and in what order. |
All of it comes from the same package the API validates against and this site renders, so there is no second copy that can drift out of date.
Prompts
diagnose_funnel— read the store report, the funnel and the friction replays together, name the biggest leak, and say explicitly what not to change. A rate already beating its band is the thing to protect. It reports which engine counted the funnel, and for an app with PostHog linked it reads the friction recordings to turn "people stop here" into why.design_paywall— work through the published evidence and produce a specific design, with each decision tied to a figure and the rejected options named.build_app— build an app end to end in the Studio, verifying each step in the running app before the next.submit_app— get an app onto the App Store in the order Apple accepts.design_store_screenshots— plan and render a screenshot set from real captures.find_app_ideas— walk App Store categories and keep the ideas worth building.