Amazon Business Integrations MCP Server
OfficialRelated Servers
Alternatives to Amazon Business Integrations MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to access Ramp's developer documentation and API schemas through natural language queries. Provides contextual answers about API endpoints, authentication methods, data relationships, and implementation patterns for developers building on Ramp's platform.4-
- AlicenseNot gradedqualityFmaintenanceEnables developers to access kintone API specifications, field type documentation, and development best practices through natural language queries. Supports API request validation and provides comprehensive development guidance for kintone customizations.22 npmMIT
- FlicenseBqualityDmaintenanceEnables natural language exploration and execution of Amazon Selling Partner API operations, with automatic parameter validation, code generation, and OAuth2 token management.3-
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to comprehensive Safaricom Daraja API documentation for all 22 M-Pesa APIs through searchable tools, enabling developers to query payment processing, transaction management, and business operations documentation.16MIT
- 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
- AlicenseAqualityAmaintenanceEnables querying and interacting with Adobe VIP Marketplace Partner API documentation through structured tools and prompts, allowing users to search endpoints, validate requests, generate code, and get operational tips.20Apache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'search-documentation' is for finding relevant documentation through semantic search, while 'read-documentation' is for retrieving the full content of specific documents. There is no overlap in functionality, and the descriptions clearly differentiate their roles in the documentation workflow.
Both tools follow a consistent verb-noun pattern ('search-documentation' and 'read-documentation'), which is clear and predictable. The minor inconsistency is the use of hyphens instead of underscores, but this is consistent across both tools, so it does not cause confusion.
With only 2 tools, the server feels under-scoped for its purpose of Amazon Business API integrations. While the tools cover documentation search and retrieval, there are no tools for actual API operations (e.g., ordering, product search, user management), which are implied by the server name and documentation paths. This limited set may hinder agent effectiveness in performing integration tasks.
The tool surface is severely incomplete for an Amazon Business Integrations server. It only provides documentation tools, missing all core API operations like creating orders, searching products, managing users, or generating reports. This creates significant gaps that will cause agent failures when attempting to perform actual integration tasks beyond reading documentation.