partner-center-mcp

An MCP server that helps you build against the Partner Center REST API: scenario discovery, ready-to-run REST examples, current authentication guidance, an auth deprecation linter, archived-.NET-SDK → REST migration, error decoding, and reference. Grounded in a curated, date-versioned knowledge pack plus live Microsoft Learn doc fetch. It holds no credentials and makes no live Partner Center calls — it is a knowledge & codegen assistant.

Unofficial, community project — not affiliated with, sponsored, or endorsed by Microsoft. "Partner Center" and "Microsoft" are trademarks of Microsoft, used here only descriptively.

Why

The Partner Center .NET SDK (3.4.0) was archived in June 2023; Microsoft directs partners to the REST APIs. Deprecated auth (the retired graph.windows.net audience) still causes 401 / 900420 failures, and from 2026-04-01 App+User API usage enforces MFA. This server steers you to the current REST + auth patterns and decodes the errors you hit along the way.

How it works

Your MCP host (Claude Code, Cursor, Copilot, VS Code…) talks to this server over the MCP protocol (stdio by default, or HTTP). The server answers from a curated knowledge pack that is zod-validated at load and grounded in official Microsoft Learn docs — falling back to a cached live doc search only when needed. It never sees your credentials and never calls Partner Center.

flowchart LR
  subgraph Host["MCP host (Claude / Cursor / Copilot / VS Code)"]
    LLM["LLM agent"]
  end
  LLM -->|"MCP protocol"| T{"Transport<br/>stdio · HTTP"}
  T --> S["partner-center-mcp"]
  S --> Tools["26 tools<br/>list/get scenario · generate_call<br/>validate_request · plan_purchase<br/>explain_lifecycle · lookup_error · diagnose · …"]
  S --> RP["Resources & Prompts<br/>pc://… · migrate / diagnose / plan"]
  Tools --> KP[("Knowledge pack<br/>data/*.json")]
  KP -. "zod-validated at load" .-> Tools
  Tools -->|"fallback (cached)"| ML[("Microsoft Learn<br/>live doc search")]
  KP -. "docUrl + lastVerified" .-> CI[["Weekly doc-freshness CI<br/>opens an issue on high-severity drift"]]

A typical call: the agent picks a tool (e.g. pc_generate_call), the server looks the scenario up in the pack, and returns the verified method, path, headers, a ready code sample, and gotchas — each carrying the docUrl it was verified against.

Run

npx partner-center-mcp

No configuration, API keys, or network access to Partner Center required.

Requires Node.js 20 or newer. (0.9.0 dropped Node 18, which reached end of life in April 2025.)

Add to your MCP host

The server speaks MCP over stdio, so any MCP-capable host works — there's nothing host-specific to install. Use whichever config your host expects:

VS Code (.vscode/mcp.json) and Visual Studio (.mcp.json):

{ "servers": { "partner-center": { "command": "npx", "args": ["-y", "partner-center-mcp"] } } }

GitHub Copilot — Copilot reads the same .vscode/mcp.json (VS Code) / .mcp.json (Visual Studio) shown above; no extra config needed.

Cursor (.cursor/mcp.json) and Windsurf (~/.codeium/windsurf/mcp_config.json):

{ "mcpServers": { "partner-center": { "command": "npx", "args": ["-y", "partner-center-mcp"] } } }

Claude Code:

claude mcp add partner-center -- npx -y partner-center-mcp

Claude Desktop (claude_desktop_config.json), Cline, and Zed use the same mcpServers shape as Cursor above.

Tip: also add the Microsoft Learn MCP server (https://learn.microsoft.com/api/mcp) alongside this one for broad documentation search.

Re