amazon-agent-atlas-mcp
Related Servers
Alternatives to amazon-agent-atlas-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceEnables users to access, search, and get recommendations from AWS documentation through natural language queries. Supports both global AWS documentation and AWS China documentation with tools to fetch pages, search content, and discover related resources.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes Amazon Selling Partner API tools for sellers to manage orders, inventory, listings, pricing, analytics, and reports via natural language.4 npm1AGPL 3.0
- FlicenseBqualityDmaintenanceProvides semantic search and data retrieval capabilities over a knowledge base with multiple tools including keyword search, category filtering, and ID-based lookup with in-memory caching.5-
- AlicenseNot gradedqualityCmaintenanceEnables external agents to retrieve knowledge with source context through MCP tools for querying, listing collections, and obtaining document summaries.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to research Amazon reviews and voice-of-customer signals through read-only tools for paginated reviews, complaint evidence, rating summaries, media filtering, and side-by-side comparisons of two products.56 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Zendesk ticket data for customer support analysis and insights. It supports searching tickets by tags or keywords, retrieving ticket details, and analyzing agent performance and service trends.-
TDQS
Scored across 4 tools
The tools are mostly distinct: tags and search both help discover tools, but by different routes (tag browsing vs. query search). get_schema and execute are clearly separate for detail retrieval and execution. Minor overlap exists between tags and search, but descriptions sufficiently clarify the difference.
Names are simple and lowercase, but not fully consistent: 'tags' is a noun while 'search', 'get_schema', and 'execute' are verbs (or verb_noun in the case of get_schema). There is no chaotic mixing of conventions, but the pattern is not uniform.
With 4 tools, the set is well-scoped for its purpose: discover by tag, search, get schema, and execute. Every tool serves a distinct role in the workflow and none is superfluous.
The set covers the core lifecycle of browsing, searching, schematizing, and executing remote tools. A minor gap is the lack of a direct 'list all tools' operation; discovery relies on tags or search, but the workflow is otherwise complete.