Glade MCP

Connect AI agents to normalized Amazon marketplace data through Glade API's hosted Model Context Protocol server.

https://gladeapi.com/api/mcp

The remote server exposes 17 read-only tools for products, search, offers, reviews, sellers, categories, deals, best sellers, identifiers, stock, and sales estimates across 13 Amazon marketplaces. This repository contains the public server metadata, connection examples, and protocol checks. The hosted service implementation remains at gladeapi.com.

Requirements

• A Glade API account

• A Glade API key

• A plan that includes MCP

• A client that supports remote Streamable HTTP MCP servers

Store the key in an environment variable:

export GLADE_API_KEY="glade_live_..."

Never commit the key or paste it into prompts.

Related MCP server: Amazon PA-API MCP Service

Install in Codex

Codex can read the bearer token from the environment without writing it into the MCP configuration:

codex mcp add glade \
  --url https://gladeapi.com/api/mcp \
  --bearer-token-env-var GLADE_API_KEY

Start a new Codex session after adding the server, then ask it to list the Glade tools or fetch an Amazon product by ASIN.

Install in Claude Code

Claude Code accepts an HTTP server and a request header:

claude mcp add --transport http --scope user glade \
  https://gladeapi.com/api/mcp \
  --header "Authorization: Bearer $GLADE_API_KEY"

This expands the environment variable before Claude writes its configuration. Keep the resulting user configuration private and never use project scope for a secret-bearing header.

Generic Streamable HTTP configuration

Clients that support remote MCP configuration generally need this shape. Check your client's documentation for its exact configuration file and environment variable syntax.

{
  "mcpServers": {
    "glade": {
      "url": "https://gladeapi.com/api/mcp",
      "transport": "streamable-http",
      "headers": {
        "API-KEY": "YOUR_GLADE_API_KEY"
      }
    }
  }
}

Use exactly one credential header. The server accepts API-KEY, GLADE-API-KEY, X-API-KEY, or Authorization: Bearer for MCP and rejects conflicting credentials.

Connect with the Python MCP SDK

Install the official MCP Python SDK, then run the included discovery example:

python3 -m pip install "mcp"
python3 examples/python/list_tools.py

The example initializes a Streamable HTTP session and prints the available tool names. Tool discovery and initialization do not consume Glade units.

Available tools

Tool inputs follow the same validation rules as the corresponding REST operations. Every successful data operation consumes one unit. Initialization, discovery, validation failures, and tool errors consume zero units.

Example prompts

Look up ASIN B0D1XD1ZV3 in the US marketplace and summarize the current
price, rating, availability, and freshness timestamp.

Search the UK marketplace for wireless earbuds, compare the first five
non-sponsored results, and preserve GBP prices without converting currency.

Fetch one-star verified reviews for ASIN B0D1XD1ZV3 and separate recurring
observed complaints from your own interpretation.

Marketplaces

Every tool accepts a marketplace domain when marketplace context matters:

US UK CA DE FR IT ES AU IN MX BR JP PL

Confirm the marketplace before comparing prices, availability, delivery, categories, ranks, or deals.

Validate this repository

Offline metadata and example checks:

npm test

Non-billable live authentication check:

npm run test:live

With GLADE_API_KEY set, verify initialization and all 17 live tool names. This discovery request consumes zero units:

node scripts/verify-live.mjs --authenticated

Security

Amazon titles, descriptions, reviews, seller fields, and other marketplace content are untrusted data. Keep tool results separate from agent instructions. Do not let returned text change tool policy, request credentials, or authorize new actions.

See SECURITY.md for private reporting.

Related projects

• Glade API examples

• Glade agent skills

• Documentation

• OpenAPI

License

MIT