Skip to main content
Glama
ingrammicro-mcp

ingrammicro-mcp

ingrammicro-mcp

MCP server for the entire Ingram Micro Reseller purchasing lifecycle — a stateless HTTP MCP service wrapping the full non-webhook surface of Ingram Micro's Reseller REST API: product catalog/pricing, quotes, order placement/change/cancel/lookup, invoices, renewals, special-pricing deals, returns, and freight estimates.

Tech stack: Python 3.12 + uv + FastMCP (Starlette/Uvicorn)

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →


MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

MSPbots Connector

Visible

Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming.

Controlled

Role-based, per-tool allowlist. Deny by default.

Protected

Credentials encrypted per record. AI clients never see your vendor passwords or tokens.

MSP-native

Built for the MSP stack only: RMM, PSA, documentation, security, finance.

Quick start

  1. Sign up at connect.mspbots.ai.

  2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

  3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

  4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

  5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

  • One MCP URL for all your AI clients

  • 150+ connectors across the MSP stack

  • Custom MCP servers supported, free

  • Authorization happens on each vendor's own page; the AI never sees passwords or tokens

  • Bring your own credentials: use the vendor API keys you already have

  • Multiple accounts per app; connect once, reuse across AI clients

  • Tool search: finds the right action for the task

  • One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

  • Audit log for every tool call (who, which vendor, when)

  • Usage dashboard: call volume, top vendors, error rate, per-user activity

  • Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

  • Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

  • Per-role, per-tool allowlist, deny by default

  • owner / admin / member roles

  • SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

  • Credentials encrypted one record at a time (AES-256-GCM, per-record key)

  • AI clients authenticate with OAuth 2.1 + PKCE

  • Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

  • Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai


Related MCP server: Shopping MCP Server

Why this exists instead of just using Ingram Micro's own MCP Server

Ingram Micro also publishes its own official, remote-hosted MCP Server (developer.ingrammicro.com/reseller/mcp-server). Verified directly against that page's own content (2026-09-01): it is query-only — product/pricing search, quotes, invoices, returns, renewals, subscriptions, and freight estimate. It never mentions "Create Order" or "Place Order" anywhere, so it cannot place a purchase order.

Rather than deploying two separate Ingram Micro connectors (their query- only MCP plus a second one just for ordering — which would mean provisioning two separate sets of credentials for the same vendor, and the agent having to pick between two connectors for overlapping capability), this server reimplements the official MCP's query capabilities itself, directly against the same underlying Reseller REST API, and adds the order-placement/change/cancel capability the official one lacks. One connector, one set of credentials, full coverage — this server is meant to fully replace Ingram Micro's own MCP Server for MSPbots' purposes, not run alongside it.

Authentication

OAuth2 client_credentials grant — pure server-to-server, no browser redirect — but via Ingram Micro's own documented shape: GET /oauth/oauth20/token with client_id/client_secret as query parameters, not the more common HTTP Basic Auth header. Verified against Ingram Micro's own published OpenAPI spec (github.com/ingrammicro-xvantage/xi-sdk-openapispec, openapispec/unified/XI-Resellers-API-Spec.json, checked 2026-09-01), not guessed.

Every real Orders/Quote-to-Order call additionally requires three business-context headers Ingram Micro's own docs mark mandatory — IM-CustomerNumber, IM-CountryCode, IM-CorrelationID — plus an optional IM-SenderID. IM-CorrelationID must be unique per transaction, so this server generates a fresh UUID for every call itself; it is not something the caller supplies.

Getting credentials is not self-serve. Per Ingram Micro's own onboarding docs, applying for API access requires:

  • An existing, active Ingram Micro reseller account in good standing

  • Current sales history with Ingram Micro

  • Sandbox testing, then a formal app-approval submission (~2 business days)

This is a real prerequisite, not a formality — confirm the tenant already has an active Ingram Micro reseller relationship before attempting to provision credentials for this server.

Since this is a stateless multi-tenant service, the token is not cached — every tool call re-authenticates from scratch (same pattern as cisco-umbrella-mcp/covedataprotection-mcp/webroot-mcp).

HEADER Authorization Parameters

Header

Type

Required

Default

Allowed values

Description

Example

X-IngramMicro-Client-Id

string

Yes

None

None

Client ID for OAuth2 client_credentials

abc123...

X-IngramMicro-Client-Secret

string

Yes

None

None

Client Secret for OAuth2 client_credentials

xyz789...

X-IngramMicro-Customer-Number

string

Yes

None

None

Ingram Micro reseller account number (maps to upstream IM-CustomerNumber), e.g. 20-222222

20-222222

X-IngramMicro-Country-Code

string

Yes

None

None

Two-letter ISO country code (maps to upstream IM-CountryCode)

US

X-IngramMicroCloud-Api-Key

string

No

None

None

API key for the separate IM Cloud / CloudBlue Marketplace API — only needed to call ingrammicro_cloud_list_subscriptions / ingrammicro_cloud_get_subscription

ck_abc123...

X-IngramMicroCloud-Customer-Id

string

No

None

None

Customer id in the IM Cloud Marketplace (not the same id space as X-IngramMicro-Customer-Number above)

cust-42

X-IngramMicroCloud-Base-Url

string

No

INGRAMMICRO_CLOUD_BASE_URL env value

None

Per-request override of the Cloud Marketplace (Subscriptions) base URL — this reseller's host is region/tenant-specific, not a public constant (see Known Gaps); only needed if the env default is wrong or unset for this tenant

https://api.cloud.im/marketplace/na

X-IngramMicroCloud-Products-Client-Id

string

No

None

None

Basic-auth client id for the IM Cloud Marketplace Products API — a third, independent credential bundle, only needed to call ingrammicro_cloud_list_products

pid-abc123...

X-IngramMicroCloud-Products-Client-Secret

string

No

None

None

Basic-auth client secret for the same /token exchange

psecret-xyz789...

X-IngramMicroCloud-Products-Marketplace

string

No

None

None

Marketplace/region code sent in the /token request body

us

X-IngramMicroCloud-Products-Subscription-Key

string

No

None

None

X-Subscription-Key value issued at onboarding — sent on every call, including /token itself

066a6b...

X-IngramMicroCloud-Products-Base-Url

string

No

None

None

This reseller's IM Cloud Marketplace Products API host (not a public constant — see Known Gaps)

https://api.cloud.im

Missing any of the four Resellers headers returns 401 Unauthorized. The X-IngramMicroCloud-* and X-IngramMicroCloud-Products-* headers are independent of those four and of each other: a caller that never sends them still gets full access to every other tool in this server — only ingrammicro_cloud_list_subscriptions / ingrammicro_cloud_get_subscription / ingrammicro_cloud_list_products themselves return a not_configured error envelope when their own bundle is absent or incomplete.

Quick Start

docker compose up --build

The server starts on http://localhost:8080.

Local (uv)

uv sync
python -m ingrammicro_mcp

Health Check

curl http://localhost:8080/health
# {"status": "ok"}

No credentials are required for the health endpoint.

Environment Variables

Variable

Default

Description

MCP_TRANSPORT

stdio

http (production) or stdio (local dev)

MCP_HTTP_PORT

8080

Listening port

MCP_HTTP_HOST

0.0.0.0

Listening host

AUTH_MODE

gateway

gateway (per-request headers, SOP-compliant) or env (shared credential, local dev only)

INGRAMMICRO_CLIENT_ID / _CLIENT_SECRET / _CUSTOMER_NUMBER / _COUNTRY_CODE

—

Only used in env mode

INGRAMMICRO_SENDER_ID

MSPbots

IM-SenderID value sent on every call

INGRAMMICRO_BASE_URL

https://api.ingrammicro.com

Override for sandbox testing (see Known Gaps — the exact sandbox URL is unverified)

INGRAMMICRO_CLOUD_API_KEY / _CLOUD_CUSTOMER_ID

—

Only used in env mode, for ingrammicro_cloud_list_subscriptions / ingrammicro_cloud_get_subscription

INGRAMMICRO_CLOUD_BASE_URL

— (no default)

IM Cloud / CloudBlue Marketplace API host — no hardcoded default since the exact host is unverified (see Known Gaps); the tool returns not_configured until this is set

INGRAMMICRO_CLOUD_PRODUCTS_CLIENT_ID / _CLIENT_SECRET / _MARKETPLACE / _SUBSCRIPTION_KEY / _BASE_URL

—

Only used in env mode, for ingrammicro_cloud_list_products — a third, independent credential bundle (see Authentication above)

Tool List

28 tools: 24 covering every non-webhook endpoint in Ingram Micro's Resellers API, plus 4 for the separate IM Cloud Marketplace product line (see below — subscriptions/change-orders and products are independent credential bundles). Every order-placing/modifying tool spends real money against the reseller's Ingram Micro net-terms account — Ingram Micro does not support credit-card API ordering, only net-terms trade credit, so a mistaken order is a real invoice, not a rejected charge.

Catalog (corresponds to the official MCP: Product Info & Pricing)

Tool

Description

Method + Path

ingrammicro_search_products

Search the product catalog by keyword/vendor/category

GET /resellers/v6/catalog

ingrammicro_get_product_detail

Get product details by Ingram Part Number

GET /resellers/v6/catalog/details/{ingramPartNumber}

ingrammicro_get_product_detail_by_reference

Get product details by vendor part number / subscription plan id or name

GET /resellers/v6/catalog/details

ingrammicro_get_price_and_availability

Get real-time price and stock

POST /resellers/v6/catalog/priceandavailability

Quotes (corresponds to the official MCP: Quotes)

Tool

Description

Method + Path

ingrammicro_search_quotes

Search quotes

GET /resellers/v6/quotes/search

ingrammicro_get_quote

Get quote details

GET /resellers/v6/quotes/{quoteNumber}

ingrammicro_create_quote

Create a quote (reserves the price, does not place an order)

POST /resellers/v6/quotes/create

ingrammicro_validate_quote_to_order

Validate a quote before converting it to an order, returns required fields

GET /resellers/v6/q2o/validatequote

Orders (corresponds to the official MCP: Orders, but the official one is read-only; placing/modifying/cancelling orders are capabilities the official one does not have)

Tool

Description

Method + Path

Main parameters

ingrammicro_create_order

Place an order: stock / direct-ship / licensing / warranty SKUs

POST /resellers/v6/orders

customer_order_number (required), lines (required), ship_to_info, end_user_info, reseller_info, shipment_details, vendor_auth_number (required for warranty orders)

ingrammicro_create_cloud_order

Place an order: cloud subscription / Quote-to-Order / Configure-to-Order (asynchronous, the result is pushed via webhook and is not in this response)

POST /resellers/v7/orders

exactly one of quote_number or lines (one must be given)

ingrammicro_modify_order

Modify an order: only orders with the customer-hold flag, within 24 hours after placing

PUT /resellers/v6/orders/{orderNumber}

order_number (required), action_code (e.g. "release"), lines (ADD/UPDATE/DELETE)

ingrammicro_cancel_order

Cancel an order: only before it has been released to the warehouse

DELETE /resellers/v6/orders/{OrderNumber}

order_number (required)

ingrammicro_get_order

Get details / shipping status of a single order

GET /resellers/v6.1/orders/{ordernumber}

ingrammicro_search_orders

Search orders by PO number / status / product

GET /resellers/v6/orders/search

Invoices (corresponds to the official MCP: Invoices)

Tool

Description

Method + Path

ingrammicro_search_invoices

Search invoices

GET /resellers/v6/invoices

ingrammicro_get_invoice

Get invoice details

GET /resellers/v6.1/invoices/{invoiceNumber}

Renewals (corresponds to the official MCP: Subscriptions/Renewals)

Tool

Description

Method + Path

ingrammicro_search_renewals

Search renewal opportunities

POST /resellers/v6/renewals/search

ingrammicro_get_renewal

Get renewal details

GET /resellers/v6/renewals/{renewalId}

Deals (special pricing / Special Bid; not listed separately in the official MCP, but also a query-type capability)

Tool

Description

Method + Path

ingrammicro_search_deals

Search special pricing / Special Bid

GET /resellers/v6/deals/search

ingrammicro_get_deal

Get deal details

GET /resellers/v6/deals/{dealId}

Returns (corresponds to the official MCP: Returns)

Tool

Description

Method + Path

ingrammicro_search_returns

Search return (RMA) requests

GET /resellers/v6/returns/search

ingrammicro_get_return

Get return details

GET /resellers/v6/returns/{caseRequestNumber}

ingrammicro_create_return

Submit a return request

POST /resellers/v6/returns/create

Freight (corresponds to the official MCP: Freight & Shipping)

Tool

Description

Method + Path

ingrammicro_get_freight_estimate

Freight estimate

POST /resellers/v6/freightestimate

Cloud Marketplace (new — IM Cloud API, distinct from the Resellers API above)

A separate Ingram Micro product line (Cloud Marketplace subscriptions, change orders, and products, e.g. Microsoft 365 plans/SKUs), itself split into two independent sub-APIs with two different auth schemes and credential headers — see HEADER Authorization Parameters above. Neither requires the four Resellers headers; ingrammicro_cloud_list_subscriptions, ingrammicro_cloud_get_subscription, and ingrammicro_cloud_create_change_order share one credential bundle, ingrammicro_cloud_list_products uses a separate, independent one.

Tool

Description

Method + Path

ingrammicro_cloud_list_subscriptions

List this customer's Cloud Marketplace subscriptions (filterable by status, creation-date range) — use to find the subscription to add/remove seats on

GET /subscriptions

ingrammicro_cloud_get_subscription

Fetch one Cloud Marketplace subscription's full detail (billing period, subscription period, product lines with mpn/quantity, renewal date) by id — use before placing a quantity-change order on a subscription found above

GET /subscriptions/{id}

ingrammicro_cloud_create_change_order

Add or remove license seats on an existing Cloud Marketplace subscription (quantity is the new TOTAL, not a delta) — asynchronous, returns only the initial acknowledgement

POST /orders

ingrammicro_cloud_list_products

Look up sellable Cloud Marketplace products by vendor code (filterable by mpn/name/serviceName, paginated) — use to find a Microsoft 365 (or other vendor) SKU mpn/name to quote

GET /products

Complex nested parameters (lines/ship_to_info/end_user_info/reseller_info/shipment_details/additional_attributes/products/returns, etc.) are passed as dict/list[dict]; see each tool's own parameter description for the exact fields (field names have been verified against the official OpenAPI spec).

ingrammicro_search_quotes/ingrammicro_create_quote/ingrammicro_get_freight_estimate additionally require a requester_email parameter (maps to upstream IM-CustomerContact/CustomerContact: the email of the logged-in user making the request) - this is the caller's personal identity information, not a tenant-level credential, so it is a tool parameter rather than a gateway Header.

Test Example

curl -X POST http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-IngramMicro-Client-Id: <client_id>" \
  -H "X-IngramMicro-Client-Secret: <client_secret>" \
  -H "X-IngramMicro-Customer-Number: 20-222222" \
  -H "X-IngramMicro-Country-Code: US" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "ingrammicro_validate_quote_to_order",
      "arguments": { "quote_number": "QUO-14551943-D2Y9L9" }
    }
  }'

⚠️ This is a public repository; do not write sensitive information such as real client_id/client_secret/customer_number into any committed file.

API Reference

Known Gaps

  • ⚠️ Not yet verified against a real Ingram Micro account. This build was written entirely from Ingram Micro's own published OpenAPI spec — schema/tool count confirmed via the real MCP protocol (tools/list, 24 tools) and unit tests passing, but no call has been exercised against a real, credentialed Ingram Micro reseller account. Getting one requires an existing reseller relationship with sales history (see Authentication) — needs re-verification once real sandbox or production credentials are available.

  • Sandbox base URL is unconfirmed. Ingram Micro's own sources disagree: the support/auth documentation references a https://api.ingrammicro.com:443/sandbox path, while the official OpenAPI spec's own servers block lists a single URL (https://api.ingrammicro.com:443/) labeled "Sandbox" with no /sandbox suffix. INGRAMMICRO_BASE_URL is fully overridable specifically so this can be corrected without a code change once confirmed.

  • IM-ApplicationID vs IM-SenderID: Ingram's own spec documents Invoices/Deals-details as requiring IM-ApplicationID while every other endpoint documents the identical concept as IM-SenderID. Treated as a spec-naming inconsistency rather than two different things — this server sends both headers with the same configured sender id on every call rather than guessing which name a given endpoint actually validates.

  • Webhooks (Order Status, Stock Update) are out of scope. These are inbound push notifications Ingram Micro sends to a callback URL a reseller registers — not something an MCP tool (which the agent calls) can meaningfully wrap. ingrammicro_create_cloud_order (v7) is documented as asynchronous specifically because its real result arrives via this webhook mechanism, not in the tool's own response — there is no tool here to receive or poll for that result; a separate webhook receiver component would be needed for that, out of scope for this build.

  • Complex nested body parameters (lines, ship_to_info, end_user_info, reseller_info, shipment_details, additional_attributes) are passed through as dict/list[dict] rather than fully typed as individual Python parameters — the real request bodies have dozens of optional nested fields per object (verified against the spec, field names are accurate), but modeling every one as a typed parameter was out of scope. Field names/shapes are documented in each parameter's own description.

  • IM Cloud Marketplace API (ingrammicro_cloud_list_subscriptions, ingrammicro_cloud_get_subscription) base URL and auth exchange are unverified against Ingram's own deployment — and now have a specific reason to suspect the auth exchange is wrong. This client was built against the independently-verified CloudBlue "Simple API" contract (Ingram's Xvantage Cloud Marketplace is built on CloudBlue Connect), since Ingram's own two hosted copies of this spec (developer.ingrammicro.com's Cloud Marketplace API PDF and apidocs.cloud.im) could not be reached from the environment this tool was built in (PRD-21595). A later build (PRD-21597, below) did reach developer.ingrammicro.com's PDF directly (apidocs.cloud.im still ECONNRESETs) — and that PDF documents a Basic-auth POST /token -> Bearer-token exchange with a static X-Subscription-Key header on every call, not this tool's assumed direct-API-key-as-Bearer-token shape. Not fixed here (out of scope for PRD-21597, which only adds ingrammicro_cloud_list_products, and still out of scope for PRD-21596, which only adds the get-by-id method on the same client/credential bundle so it inherits this exact open question rather than introducing a new one — fixing it would mean reworking PRD-21595's already-merged header/config contract, a separate, larger change than "add one more read method") — whoever picks this gap up next should start from developer.ingrammicro.com/sites/default/files/2025-11/Cloud%20Marketplace%20API.pdf directly rather than re-attempting apidocs.cloud.im. INGRAMMICRO_CLOUD_BASE_URL has no hardcoded default specifically so the base URL can be set once confirmed, same pattern as the Resellers sandbox-URL gap above — only cloud_api_client.py's internals would need to change, not the tools' parameters or any other file. PRD-21596 added a per-request override (X-IngramMicroCloud-Base-Url) for the tenant/region-specific-host half of this gap — a caller no longer has to rely on one server-wide env value if a given reseller's host differs; the auth-exchange suspicion above is unaffected by this and still open. The same override applies to ingrammicro_cloud_create_change_order (PRD-21598) and ingrammicro_cloud_get_subscription (PRD-21596) too — all three tools share the same CloudMarketplaceClient/_base_url.

  • ingrammicro_cloud_get_subscription's by-id lookup is not known to be customer-scoped (PRD-21596): unlike ingrammicro_cloud_list_subscriptions, which sends customerId as a query filter, the by-id endpoint per apidocs.cloud.im's own example (GET /subscriptions/1000177) takes no customer parameter at all — this client relies entirely on the upstream API scoping the returned subscription to what the caller's api_key can see. Not independently confirmed (same "not yet verified against a real account" caveat as the rest of this API); if a real account call returns a subscription outside the expected tenant, that is this assumption failing, not a bug in this repo's request shape.

  • **IM Cloud change orders (ingrammicro_cloud_create_change_order, PRD-21598) share the same unverified base URL / auth exchange as ingrammicro_cloud_list_subscriptions above (same client, same gap) — plus one more open question of its own: whether Ingram's own deployment actually requires billing_period/subscription_period/total on a quantity-only change order, or treats them as optional like the generic CloudBlue "Simple API" contract this tool was built against (docs.cloudblue.com/cbc/21.0/Simple-API/how-to-use/howto/orders/). Not fixed here — the tool already exposes all three as optional pass-through parameters, so if Ingram's deployment requires them, no code change is needed, only confirmation (see docs/tickets/PRD-21598.md, Open questions, Q1). Not verified against a real account — see Known Gaps intro and TC9 in that ticket's test cases.

  • IM Cloud Marketplace Products API (ingrammicro_cloud_list_products) auth scheme is verified against Ingram's own PDF, but the real response shape and this reseller's actual base URL are not. Unlike the subscriptions tool above, this tool's auth (Basic -> POST /token -> Bearer + X-Subscription-Key) comes directly from developer.ingrammicro.com's own "Cloud Marketplace API.pdf" ("Token Generation" / "Testing the Bearer Token" sections), fetched successfully from this build's environment. What remains unverified: the exact /products response field names against a live account (the ticket's own field list — mpn/name/vendor/serviceName/billingPeriods/ prices — is passed through unmodified, not re-modeled, so if the real API differs the mismatch will be visible rather than silently reshaped), and — same as every other base URL in this file — X-IngramMicroCloud-Products-Base-Url has no public constant and is handed out at onboarding, hence the per-request header rather than a hardcoded default.

Available Tools

24 tools
ingrammicro_cancel_orderA
DestructiveIdempotent

Cancel an order before it reaches Ingram Micro's warehouse.

    Irreversible once it fails: an order already released to the
    warehouse CANNOT be canceled through this API at all — Ingram
    Micro requires the order to still be on customer hold. Confirm
    with a human before calling; there is no way to check "is it too
    late" ahead of time other than trying and reading the error.
    

Inputs: order_number (required). Returns: result

ingrammicro_create_cloud_orderA
Destructive

Place a cloud-subscription order, or convert an existing Quote (Quote-to-Order / Configure-to-Order) into a real order. Asynchronous: this call only returns a confirmationNumber acknowledging receipt — Ingram Micro pushes the actual order result (success or error) later via its own webhook, not in this response.

    For standard stocked/direct-ship/licensing/warranty SKUs (not
    cloud, not quote-based), use ingrammicro_create_order instead.
    Real money against the reseller's net-terms account — no dry-run,
    no credit-card ordering. Always validate a quote first with
    ingrammicro_validate_quote_to_order before passing quote_number
    here.
    

Inputs: lines, notes, quote_number, ship_to_info, +9 more. Returns: result

ingrammicro_create_orderA
Destructive

Place a real purchase order for stocked, direct-ship, licensing, or warranty SKUs. Real money against the reseller's net-terms account — Ingram does not support credit-card API ordering.

    For cloud subscriptions, Quote-to-Order, or Configure-to-Order, use
    ingrammicro_create_cloud_order instead — this tool is for standard
    SKU ordering only. Confirm every SKU/quantity/price with a human
    first; there is no dry-run mode. Returns per-line success/error/
    warning counts and, on partial failure, a rejectedLineItems list
    naming exactly which lines failed and why.
    

Inputs: lines (required), customer_order_number (required), notes, ship_to_info, +9 more. Returns: result

ingrammicro_create_quoteA

Create a new quote — a price hold, not a purchase. Convert it to a real order later with ingrammicro_create_cloud_order(quote_number=...) after validating with ingrammicro_validate_quote_to_order.

Inputs: products (required), requester_email (required), deal_id, last_name, +7 more. Returns: result

ingrammicro_create_returnA
Destructive

File one or more return (RMA) requests against already-invoiced product. Each entry needs the original invoice, a quantity, primary/secondary reason, box count, and a full ship-from address — Ingram rejects a request missing any of those. Confirm with a human before filing; a filed return cannot be un-filed through this API.

Inputs: returns (required). Returns: result

ingrammicro_get_dealA
Read-onlyIdempotent

Get full detail for one special-pricing deal, including which products/vendors it covers.

Inputs: deal_id (required). Returns: result

ingrammicro_get_freight_estimateA
Read-onlyIdempotent

Estimate freight/shipping cost for a set of SKUs and quantities before placing an order — check this when shipping cost matters to the customer's decision.

Inputs: lines (required), requester_email (required), ship_to_address, bill_to_address_id, +1 more. Returns: result

ingrammicro_get_invoiceA
Read-onlyIdempotent

Get full line-level detail for one invoice.

Inputs: invoice_number (required), include_serial_numbers. Returns: result

ingrammicro_get_orderA
Read-onlyIdempotent

Get full status/line detail for one order — shipping status, tracking, per-line fulfillment. Use ingrammicro_search_orders instead if you don't already have the exact order number.

Inputs: order_number (required), vendor_number. Returns: result

ingrammicro_get_price_and_availabilityA
Read-onlyIdempotent

Get real-time price and/or stock availability for one or more SKUs — the step before placing an order, to confirm current price and that stock exists before calling ingrammicro_create_order.

Inputs: products (required), include_pricing, include_availability, availability_by_warehouse, +1 more. Returns: result

ingrammicro_get_product_detailA
Read-onlyIdempotent

Get full catalog detail for one product by its Ingram Micro part number (from ingrammicro_search_products). Use ingrammicro_get_product_detail_by_reference instead if you only have the vendor's own part number or a subscription plan id/name.

Inputs: ingram_part_number (required). Returns: result

ingrammicro_get_product_detail_by_referenceA
Read-onlyIdempotent

Get catalog detail for a product identified by the vendor's own part number, or by subscription plan id/name — for when you don't have Ingram's own part number. Exactly one of vendor_part_number, plan_id, or plan_name must be given.

Inputs: plan_id, plan_name, vendor_part_number. Returns: result

ingrammicro_get_quoteA
Read-onlyIdempotent

Get full detail for one quote — line items, pricing, expiry, and current status.

Inputs: quote_number (required). Returns: result

ingrammicro_get_renewalA
Read-onlyIdempotent

Get full detail for one renewal opportunity.

Inputs: renewal_id (required). Returns: result

ingrammicro_get_returnA
Read-onlyIdempotent

Get full detail and current status for one return (RMA) request.

Inputs: case_request_number (required). Returns: result

ingrammicro_modify_orderA
Idempotent

Change an order placed with the customer-hold flag — add/update/ delete lines, change ship-to, or release the hold.

ONLY works within roughly 24 hours of placement, and only if the order was created with the customer-hold flag (void after 24h if never released). An order placed WITHOUT customer-hold cannot be modified — this call fails. Confirm with a human before changing quantities or the shipping address.

Inputs: order_number (required), lines, notes, action_code, +2 more. Returns: result

ingrammicro_search_dealsA
Read-onlyIdempotent

Search special-pricing deals (vendor discount bids) by vendor or end customer. A deal's id can be passed as special_bid_number when placing an order, or as deal_id when creating a quote. Use this to find the exact deal id before ingrammicro_get_deal.

Inputs: page, size, vendor, deal_id, +1 more. Returns: result

ingrammicro_search_invoicesA
Read-onlyIdempotent

Search invoices by order, invoice number, date range, or status. Use this to find the exact invoice number before calling ingrammicro_get_invoice.

Inputs: page_size, page_number, invoice_date, invoice_type, +11 more. Returns: result

ingrammicro_search_ordersA
Read-onlyIdempotent

Search past/current orders by PO number, status, product, or date. Use this to find the exact order number before calling ingrammicro_get_order, ingrammicro_modify_order, or ingrammicro_cancel_order.

Inputs: page_size, order_date, page_number, vendor_name, +9 more. Returns: result

ingrammicro_search_productsA
Read-onlyIdempotent

Search Ingram Micro's product catalog by keyword, vendor, category, or SKU type. "What's the Ingram part number for Cisco switch model X" or "list Microsoft cloud SKUs with discounts" both start here. Returns matching products with Ingram/vendor part numbers; call ingrammicro_get_price_and_availability next for live pricing/stock.

Inputs: vendor, keyword, category, sku_type, +5 more. Returns: result

ingrammicro_search_quotesA
Read-onlyIdempotent

Search quotes by number, status, vendor, or end customer. Use this to find a quote's number before ingrammicro_get_quote, ingrammicro_validate_quote_to_order, or converting it to an order with ingrammicro_create_cloud_order.

Inputs: requester_email (required), status, page_size, quote_name, +5 more. Returns: result

ingrammicro_search_renewalsA
Read-onlyIdempotent

Search upcoming or past subscription/support renewals by order, vendor, end customer, or opportunity status. Use this to find the renewal id before ingrammicro_get_renewal.

Inputs: page, size, vendor, end_user, +5 more. Returns: result

ingrammicro_search_returnsA
Read-onlyIdempotent

Search return (RMA) requests by invoice, product, or status. Use this to find the exact case_request_number before calling ingrammicro_get_return.

Inputs: page, size, return_status, invoice_number, +5 more. Returns: result

ingrammicro_validate_quote_to_orderA
Read-onlyIdempotent

Validate a quote before converting it to an order, and learn which fields the vendor requires at header and line level for the Quote-to-Order call.

    Always call this before ingrammicro_create_cloud_order(quote_number=...)
    — the response's vmfAdditionalAttributes (header level) and each
    line's vmfAdditionalAttributesLines name the exact vendor-mandatory
    fields to copy into that call's additional_attributes.
    

Inputs: quote_number (required). Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with search/get pairs clearly separated by whether an exact ID is known. Potential overlaps like create_order vs create_cloud_order and get_product_detail vs get_product_detail_by_reference are explicitly disambiguated in the descriptions.

    Naming Consistency5/5

    All tools follow the consistent ingrammicro_ prefix with verb_noun snake_case naming. Verbs like get, search, create, modify, cancel, and validate are used predictably across the set, making intent easy to infer.

    Tool Count4/5

    At 24 tools, this is slightly above the typical well-scoped range, but the count is justified by the broad distribution domain covering products, orders, quotes, invoices, returns, renewals, deals, and freight. Each tool has a clear place, so the set feels substantial rather than bloated.

    Completeness5/5

    The toolset covers the core reseller workflow end-to-end: product search/detail/pricing, order placement with modification/cancellation, quote creation through validation and conversion, plus invoices, returns, renewals, deals, and freight estimates. No significant dead ends or missing lifecycle operations for the stated domain are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables eBay-backed product search, authenticated shopping carts, checkout quotes, and order management through MCP tools and resources.
      11
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable clients to sign in with OAuth and perform purchaser tasks such as browsing catalogues, checking inventory, managing stocktakes and recipes, drafting requisitions, updating buy lists, exporting reports, and processing invoices. It also supports supplier access for listing and inspecting connections, catalogues, products, purchase orders, invoices, and entitled reports.
      MIT