Skip to main content
Glama
Amazon Business Integrations MCP Server

Amazon Business Integrations MCP Server

Official

Amazon Business Integrations MCP Server

The Amazon Business Integrations Model Context Protocol (MCP) Server empowers AI-enabled developer environments by providing direct, contextual access to Amazon Business API documentation, sample code, and troubleshooting resources. This server acts as a bridge between your IDE and Amazon Business’s technical knowledge base, enabling AI models to instantly retrieve relevant API details, generate sample integration code, and offer guided solutions for common errors. You can use this MCP Server throughout your API integration process to simplify and accelerate development.

This MCP Server is currently in preview release and is intended for testing and evaluation purposes. This MCP Server is subject to Amazon’s Conditions of Use.

Features

  • Search Documentation: Search through documentation using natural language queries.

  • Read Documentation: Retrieve documentation content using references.

With these functions, you can search for and read Amazon Business API documentation to understanding various API offerings, and extract sample code during your integration.

Prerequisites

Before using the Amazon Business Integrations MCP Server, complete these steps:

  1. Ensure that you have installed an IDE that supports MCPs and developer agents, such as Amazon Q.

  2. Install node.js and npm if you do not have them on your system.

  3. Access your account ID in your Solution Provider Portal (SPP) account. You can find this ID from the Global Accounts section in SPP.

You will use this ID to complete the MCP Server configuration. If you do not have this ID, complete the API onboarding process to generate your ID. For more information, see Onboarding overview.

If you only plan to use the MCP Server to search and read Amazon Business documentation, complete Onboarding Step 1 to create your developer account and generate your account ID. If you plan to use the MCP Server to help generate code, complete Onboarding Step 1, Step 2, and Step 3 to receive the access and refresh tokens required for production API calls.

An image showing SPP portal with "Global accounts" menu highlighted.

Installation

Follow the appropriate steps below to install the MCP server in your preferred IDE:

  1. Add Amazon Business Integrations MCP Server to the MCP configuration file (for example, for Amazon Q Developer CLI, edit ~/.aws/amazonq/mcp.json by using the below JSON snippet).

  2. In the --dev-account-id=<account_id> field in the args list, provide your account ID from Prerequisites Step 3:

{
  "mcpServers": {
    "ab-integrations-mcp-server": {
      "command": "npx",
      "args": ["@amazonbusiness/ab-integrations-mcp-server@latest", "--dev-account-id=<account_id>"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Quick start

Once you’ve installed the Amazon Business Integrations MCP Server, you can ask your AI assistant questions such as:

  • “I want to build a react-based shopping application that displays products and product detail pages using Product Search API.”

  • “I want to build a shopping application that displays products using Product Search API and places orders using Ordering API.”

  • "Search for information about the Product Search API"

  • "Find documentation about authentication requirements"

  • “How can I test my Amazon Business API calls?”

Available MCP tools

search-documentation

Perform semantic searches across the documentation corpus using natural language queries. Returns relevant documentation snippets with document references.

Here is the folder structure that determines the documentationPath to use for searches in the MCP server:

📂 
├──  API Swagger Models/ - API schemas, data structures, request/response formats, field definitions, and models for building applications and generating code
├──  OAuth/ - Essential authentication and authorization documentation covering tokens, login processes, credentials, access control, and security implementation. OAuth authentication is a prerequisite for all Amazon Business API implementations.
├──  Ordering API/ - Order placement, creation, purchasing, and buying operations
├──  Product Search API/ - Product searching, catalog browsing, item discovery, and product details
├──  Reconciliation API/ - Purchase data reconciliation, transaction matching, and financial records management
├──  Reporting API/ - Order history, tracking information, payment details, and analytics reports
├──  User Management API/ - User account management and user operations
├──  Document API/ - Invoice generation, receipts, and document reports
├──  Application Management API/ - Client secrets, application management, and secret rotation
└──  Guides and FAQs/ - Step-by-step tutorials, implementation guides, frequently asked questions, best practices, getting started resources, and practical examples

Parameters

Name

Description

Schema

Required

query

Natural language search query to find documentation.

string

Yes

maxResults

Maximum number of results to return. (default: 5, maximum: 20)

number

No

documentationPath

List of documentation paths to search (e.g. API Swagger Models, OAuth, Ordering API, Product Search API) to narrow down the search results (maximum: 5).

string

No

read-documentation

Retrieve complete documentation content using document references obtained from documentation and search results.

Parameters

Name

Description

Schema

Required

documentReference

Reference to the document from the search results.

string

Yes

Authentication

The Amazon Business Integrations MCP Server does not require authentication but is subject to rate limits.

For support or questions about the MCP Server, please contact abapi-integrations@amazon.com.

Disclaimer

This MCP Server is provided as an open-source tool to allow users to access their own AI tools to query documentation and generate sample code. The sample code generated is intended solely for demonstration and educational purposes. Amazon Business makes no representations and bears no responsibility related to the accuracy, completeness, or suitability of any generated code. Amazon’s Conditions of Use apply.

Users are advised to exercise their own discretion and perform independent verification before using any code in production or critical environments. The maintainers and contributors of this project shall not be held liable for any errors, omissions, or damages arising from the use of this server or its outputs.

By using the MCP Server, you acknowledge that you are responsible for evaluating the suitability and correctness of the generated content for your specific use case.

Available Tools

2 tools
read-documentationA

Retrieve complete documentation content using a document reference.

This tool fetches the full content of documentation files identified by documentReference. The documentReference parameter is typically obtained from search-documentation results. However, when searching documentation, if a document contains documentReference: and the referenced document is relevant to the user's query, you should use read_documentation tool with as documentReference.

HIGHLY RECOMMENDED: Start by reading the following documents (using read-documentation tool) when interacting with this server:

  1. Getting started guide : "Guides and FAQs/amazon-business-apis-getting-started-guide.md"

  2. To understand authentication requirements: "OAuth/oauth-instructions.md"

Common use cases:

  • Retrieving a complete API reference document

  • Accessing full documentation sections after discovering them via search

  • Getting detailed information about specific API endpoints, parameters, or data models

  • Reading implementation guides and tutorials in their entirety

Inputs: documentReference (required).

search-documentationA

Search through documentation using a natural language query.

This tool provides semantic search capabilities across the entire API documentation corpus. It analyzes your query and returns the most relevant documentation chunks based on semantic similarity.

The results include document snippets with relevance scores and document references that can be used with the read-documentation tool to fetch complete documents. Document snippets can also contain documentReference: and if the referenced document is relevant to the user's query, you should use read_documentation tool with as documentReference.

DOCUMENTATION PATH SELECTION: Select the most specific documentation path that matches your query intent to filter the search radius:

├── API Swagger Models/ - API schemas, data structures, request/response formats, field definitions, and models for building applications and generating code ├── OAuth/ - Essential authentication and authorization documentation covering tokens, login processes, credentials, access control, and security implementation. OAuth authentication is a prerequisite for all Amazon Business API implementations. ├── Ordering API/ - Order placement, creation, purchasing, and buying operations ├── Product Search API/ - Product searching, catalog browsing, item discovery, and product details ├── Reconciliation API/ - Purchase data reconciliation, transaction matching, and financial records management ├── Reporting API/ - Order history, tracking information, payment details, and analytics reports ├── User Management API/ - User account management and user operations ├── Document API/ - Invoice generation, receipts, and document reports ├── Application Management API/ - Client secrets, application management, and secret rotation ├── Guides and FAQs/ - Step-by-step tutorials, implementation guides, frequently asked questions, best practices, getting started resources, and practical examples

Helpful Hints:

  1. If you are searching for code generation/building applications → API Swagger Model

  2. If you are searching for specific API → Use that API documentation path to narrow down the search radius

  3. If your query matches more than one documentation path, you can search across all the matching documentation paths

  4. If you are looking for guidance/examples → Guides and FAQs

  5. If uncertain → Use the most relevant API documentation path based on the core functionality described

  6. If nothing is relevant, search across all the documentation paths. DO NOT provide any documentation path

HIGHLY RECOMMENDED: Start by reading the following documents (using read-documentation tool) when interacting with this server:

  1. Getting started guide : "Guides and FAQs/amazon-business-apis-getting-started-guide.md"

  2. To understand authentication requirements: "OAuth/oauth-instructions.md"

Common use cases:

  • Finding API details by describing functionality ("how to search products")

  • Searching for specific parameters, field definitions or data models

  • Locating code examples and implementation guidance

  • Discovering endpoint requirements and constraints

Note: When you are implementing or building application, ALWAYS search for the swagger model, code snippets and any specific instructions given for generating code. Verify that Amazon Business API OAuth is implemented before implementing any APIs. It is recommended to understand and avoid common pitfalls, by using read-documentation tool with reference "Guides and FAQs/common-pitfalls.md"

Inputs: query (required), maxResults, documentationPath.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness1/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      17
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Exposes Amazon Selling Partner API tools for sellers to manage orders, inventory, listings, pricing, analytics, and reports via natural language.
      1
      -

    Appeared in Searches