Adobe VIP Marketplace Docs MCP Server
Related Servers
Alternatives to Adobe VIP Marketplace Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceExposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.147 npm2MIT
- FlicenseAqualityDmaintenanceEnables API documentation lookup and live API tools for managing Upmind platform resources like brands, products, clients, invoices, and tickets through natural language.971-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and fetch documentation content from Adobe Experience League, allowing natural language queries to retrieve Adobe product documentation and articles.-
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to search and explore API documentation from Apidog projects or OpenAPI/Swagger specifications, providing endpoint details, schemas, and project statistics through natural language queries.1,061 npm1ISC
- AlicenseAqualityAmaintenanceEnables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.7385 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search, browse, and read official Adobe Commerce / Magento documentation, including extracting code examples, navigating page sections, and looking up error codes and troubleshooting articles.65 npm-
TDQS
Scored across 20 tools
Most tools have clearly distinct purposes: browsing/searching docs, extracting structured data, and endpoint helpers are cleanly separated. The main ambiguity is among the maintenance trio (warm_vipmp_cache, refresh_vipmp_sitemap, rebuild_vipmp_index) and the overlap between vipmp_cache_stats and vipmp_server_info.
All tool names use snake_case with a vipmp prefix, and most follow a verb_vipmp_noun pattern (list, get, search, refresh, rebuild). A few deviations such as vipmp_cache_stats, vipmp_cache_clear, and vipmp_server_info put the noun first, which breaks the otherwise predictable convention.
20 tools is on the heavy side for a documentation server, especially since several are cache/sitemap/index maintenance and diagnostic utilities rather than core documentation access. Each tool is individually useful, but the set would feel better scoped if some maintenance tools were consolidated.
The surface is comprehensive for a docs server: browse, search, fetch pages, and extract endpoints, error codes, status codes, schemas, code examples, release notes, and tips. It also goes beyond reading with endpoint profiling, request validation, and code generation, so there are no obvious dead ends or missing core workflows.