# MCP Server Workflows
> Follow research-led MCP workflows for support, product, billing, customer success, and incident response.
Canonical: https://www.mcpfolio.com/workflows
- [Prepare an evidence-backed support escalation](https://www.mcpfolio.com/workflows/support-escalation-evidence-packet): Join a customer report, error telemetry, and backlog context into a reviewed engineering handoff.
- [Audit Stripe subscriptions against app entitlements](https://www.mcpfolio.com/workflows/stripe-entitlement-discrepancy-audit): Compare current billing state with Supabase access state and return a reviewed exception report without changing either system.
- [Group duplicate customer requests without losing their sources](https://www.mcpfolio.com/workflows/deduplicate-customer-feature-requests): Turn scattered support requests into problem themes linked back to the original customer evidence.
- [Turn customer calls into reviewed notes and follow-ups](https://www.mcpfolio.com/workflows/customer-call-followup-packet): Carry decisions and promised next steps from a call transcript into the account record and task tracker.
- [Prioritize product problems with customer and usage evidence](https://www.mcpfolio.com/workflows/customer-feedback-priority-brief): Compare repeated customer pain with observed feature usage and backlog context before proposing roadmap priorities.
- [Draft an incident timeline from alerts and error evidence](https://www.mcpfolio.com/workflows/incident-timeline-postmortem-draft): Bring incident records and telemetry into a source-linked postmortem draft with uncertainty preserved.
- [Find postmortem actions that slipped past the incident](https://www.mcpfolio.com/workflows/postmortem-action-followthrough): Compare postmortem commitments with the issue tracker and code changes, then prepare a reviewed overdue-action report.
- [Find the runbook for an active incident and flag stale steps](https://www.mcpfolio.com/workflows/retrieve-and-check-incident-runbook): Use the incident service and symptoms to find the matching procedure, then surface gaps for an engineer to verify.
- [Prepare an evidence-based at-risk customer review](https://www.mcpfolio.com/workflows/prepare-at-risk-customer-review): Bring together recent usage, support context, and billing identifiers for one customer before a renewal or health review.
- [Find broken product analytics events before trusting a funnel](https://www.mcpfolio.com/workflows/audit-analytics-events-against-tracking-contract): Compare an agreed tracking contract with analytics taxonomy, event data, and existing engineering work before making product decisions.