Use MCP for setup, analysis and Flows

What you need

A connected client, appropriate credential and a clear app/domain/window. Provide explicit authorization for secrets, production deploys, provider calls and sending messages.

Steps

1. For setup, ask for list_apps, choose the exact app and call get_setup_guide. Its app-specific snippets and agent instructions describe the current configuration.
2. Decide the contact path. Uploading a Shopify client secret, adding an access-token identify hook and deploying production each need the developer’s explicit approval.
3. For analytics, ask a scoped question such as “For this app and the last 30 days, show MRR movements and report history coverage.” Resolve ambiguous merchant matches with app/domain identity.
4. For Flows, list real templates, create/edit a draft and preview it. Inspect the current app scope/source acknowledgement before any live activation. Sending a queued message is a distinct delivery action.
5. For partner quality, ask for the intended app/program/cohort and original currency; keep unknown metrics visible.
6. Import contact rows only after reviewing the actual fields and source. Recheck app observations after authorized integration changes.

Expected result

Useful analysis tied to the same data layer as the product, or an explicitly reviewed draft change. MCP access does not add merchant events that your app has never emitted.

Review the tool effects

Analytics/report tools read; create/update/import/secret tools write; live status and send actions can deliver externally. Follow each canonical reference’s side-effect section. Public Markdown helps assistants read the same guides without workspace-data export.

Troubleshooting

Check schema/tool visibility first. An assistant’s suggestion is not evidence of delivery, activation or attribution. AI preview with a brief and draft_winback can call Gemini; authorize the provider request even if the draft remains unsent.

Custom definitions

Use the Flow definition contract when authoring JSON instead of choosing a template. It includes the full nested schema, scope rules and validation constraints.