Glade API

com.gladeapiPublished by gladeapi.comOfficial publisherv1.0.0Updated Oct 24, 2026

Amazon marketplace data for products, offers, reviews, sellers, search, categories, and deals.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant access to Amazon marketplace data: products, offers, reviews, sellers, search, categories and deals.

What you can do
  • Look up Amazon products and their details
  • Retrieve offers and pricing for items
  • Read customer reviews
  • Find and inspect sellers
  • Search the marketplace and browse categories
  • Surface current deals
When to use it
Useful when you need Amazon marketplace research inside an assistant session — comparing products and offers, checking reviews or sellers, or exploring categories and deals — without building your own scraping or API integration.
Requirements
A remote MCP endpoint at gladeapi.com using streamable HTTP. Requires a Glade API key from the Glade API dashboard, sent in the API-KEY header. No local runtime or environment variables are needed.
Before you install
The API key is a secret sent in the API-KEY header; keep it out of shared logs and conversations. Requests and queries go to a third-party service, which may have its own usage limits or billing. The manifest lists no tools, so confirm the available operations and any write or spend behavior before relying on it.

Installation

In SourceWeft

  1. Open Glade API in the dashboard and add it to a workspace.
  2. Connect API-KEY credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.gladeapi%2Fapi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "glade-api": {
      "type": "http",
      "url": "https://gladeapi.com/api/mcp",
      "headers": {
        "API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.