A
licenseB
qualityA
maintenanceProvides 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
partner-center-mcp
Related Servers
Alternatives to partner-center-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA 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-
- FlicenseNot gradedqualityDmaintenanceStarter scaffold for a workshop to build an MCP API testing server, intended to be extended through incremental steps.-
- AlicenseBqualityDmaintenanceA standalone MCP server for exploring the weclapp REST API v2, providing offline knowledge about entities, endpoints, and relationships, plus optional live GET probes against a tenant.171MIT
- AlicenseBqualityBmaintenanceMCP server for Microsoft Fabric REST APIs that enables data engineers and analysts to manage Fabric components using AI assistants.21944 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables testing and development against a mock S/4HANA Business Partner API, exposing customer and customer address entities through the MCP protocol.Apache 2.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
ResponsivenessSlow