pc_get_scenario
Full detail for one scenario: method, path, headers, examples, gotchas.
How to use it
Project documentation lists pc_get_scenario for the Partner Center MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Partner Center MCP
npx -y partner-center-mcpOther tools in Partner Center MCP (27)
Current auth guidance for app-only / app+user, per national cloud, with GDAP + MFA notes.
Build a ready-to-send request: fills path placeholders, generates MS-RequestId/MS-CorrelationId, and a body skeleton from the scenario's fields.
Lint an auth/client snippet for retired patterns (graph.windows.net, ADAL, archived SDK, AzureAD PS).
Paste a raw error response → decoded code, likely scenarios, and the correlation id for support.
Map a symptom to likely causes, fixes, and relevant scenarios.
What changed between pack releases: scenarios added, removed, or whose route, auth, fields or constraints moved.
What you can do to a subscription in its current state: legal operations, the field each precondition reads, and the errors a failed precondition returns.
Emit a current REST call (curl/csharp/typescript/powershell) with auth/retry/pagination helpers. Never the archived SDK.
Look up enum values (billingCycle, termDuration, targetView, transitionType, status, …).
Base URLs, headers, versioning, sandbox, rate limits, national-cloud differences.
Field dictionary for resources (Customer, Subscription, Order, Invoice, migration schedules, …).
List supported REST scenarios, optionally filtered by area.
Decode an error code: causes, remediation, and the scenarios it commonly hits.
Translate archived .NET SDK code into the equivalent REST scenario(s).
Ordered CSP customer onboarding (account linking): invite → verify relationship → confirm agreement → transact.
Ordered GDAP onboarding workflow (create → approve → verify) over Microsoft Graph.
Ordered call sequence from cart to provisioned subscriptions, with the cancellation and add-on branches.
For any scenario, the ordered calls that produce the ids its path needs, and the parameters you supply yourself.
The ordered New Commerce purchase workflow: product → SKU availability → cart → checkout → subscriptions.
Ordered reconciliation workflow (invoice → billed/unbilled line items → statement).
Ordered call sequence for one lifecycle change: seats up/down, upgrade, cancel, renewal changes, suspend, reactivate, migrate, transfer.
Ordered billing-ownership transfer workflow (create → poll → verify).
Ordered user offboarding: remove licenses → strip roles → delete user (30-day restore window).
Ordered user onboarding: create user → assign licenses → grant roles → verify.
Fetch live Microsoft Learn excerpts. The fallback when the curated pack has no answer.
Lint a REST call (method, URL, headers, auth) against the known scenarios.
Deprecations & deadlines (MFA enforcement, graph.windows.net, v1→v2 reconciliation, …).