MCP Server List

Request Microsoft MCP Center review

Microsoft’s curated showcase of remote MCP servers for Azure API Center customers, onboarded through one public GitHub issue thread.

Post one onboarding comment on Microsoft’s MCP Center thread; curated review and listing remain external. This action is separate from the qualifying submission minimum.

Verified onboarding comment on the maintainer threadSources checked

What to prepare

  • A public remote MCP server with an https Streamable HTTP endpoint (local servers are not yet showcased).
  • A declared authentication type; remote servers with OAuth 2.1 are favored.
  • A category from: Developer Tools, Productivity, Data & Analytics, Business Services, Cloud & Infrastructure, Other.
  • No existing request in the thread for the repository, endpoint or server name.

One comment, curated review

The service posts a single comment in the format Microsoft requests and keeps its exact URL as the receipt. It never posts twice for the same server. Microsoft decides inclusion, and favors remote servers that support OAuth 2.1.

Submission workflow

  1. Run the free preflight to check the thread is open and scan its full history for duplicates.
  2. Review the exact comment: MCP type, name, description, OAuth 2.1 support, repository, icon URL and category.
  3. Authorize it; the service account posts one comment and reads it back.
  4. Track Microsoft’s curated review (about 1-2 weeks). A comment is not a listing.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • A closed or locked thread, or an existing request for the same server.
  • A local-only server, or one Microsoft does not choose to showcase.

Primary sources

Checked 2026-11-04. Follow the destination’s current instructions if its requirements change.

← Compare all destinations