Skip to main content
Glama

Related Servers

Alternatives to partner-center-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Provides a reference MCP server that implements every MCP feature so client, gateway, and runtime authors can test against a single endpoint, and publishes a service contract describing its capabilities.
      31
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only local MCP server that lets harnesses query Microsoft Intune devices, policies, apps, enrollment, and RBAC using the signed-in user's delegated Microsoft Graph access.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A simple demonstration MCP server that provides an echo tool and resource for learning how to build MCP servers. Serves as a starting point and template for creating custom MCP server implementations.
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that generates MCP servers. Give it an API definition - OpenAPI 3.0/3.1 or a Postman collection or extend an existing server - and it scaffolds a complete, runnable, ownable TypeScript or Python MCP server for that collection of APIs.
      4
      64 npm
      1
      AGPL 3.0

    TDQS

    A4.4/5.0

    Scored across 29 tools

    Disambiguation4/5

    The pc_* prefix and explicit cross-references keep most tools distinct, and the error-handling trio is cleanly split by input type (raw response vs isolated code vs prose). However, pc_plan_purchase and pc_plan_order_lifecycle overlap in the cart/checkout/subscription-resolution steps, so an agent could plausibly select the wrong planner.

    Naming Consistency4/5

    Nearly all tools follow a pc_<verb>_<noun> pattern, and the shared prefix makes the family easy to recognize. Minor deviations like pc_auth_guidance, pc_whats_new, and pc_diagnose break the otherwise consistent verb-noun convention, so it is not a perfect 5.

    Tool Count2/5

    At 29 tools, this clearly exceeds the 25-tool threshold and feels heavy for an agent to reason about. Several families—especially the ten pc_plan_* tools and the three error/lookup tools—could reasonably be consolidated into parameterized variants without losing functionality.

    Completeness5/5

    The surface covers the full knowledge lifecycle: discover scenarios, inspect details, build or validate requests, generate code, decode errors, plan business workflows, check auth, track deprecations, and explain policies. Cross-references leave no obvious dead ends, and pc_search_docs plus pc_plan_prerequisites fill gaps not covered by curated workflows or the bundled pack.

    Maintenance

    ActivitySlowing
    ResponsivenessLimited data