Live Amazon product, review, search, deal, offer/stock and seller data across 23 marketplaces.
Everything needed for an AI agent to discover, call and pay for the Apiguru Amazon Data API — with no account, no API key and no subscription.
The existing backend is not modified by any of this. Not one line.
| Client | How |
|---|---|
| Claude Code | claude mcp add --transport http apiguru https://mcp.apiguru.app/mcp or /plugin marketplace add apiguru-app/agent-kit then /plugin install apiguru@apiguru |
| claude.ai, Claude Desktop, ChatGPT | add connector https://mcp.apiguru.app/account and sign in |
| Codex CLI | codex mcp add apiguru --url https://mcp.apiguru.app/mcp |
| Cursor | Add to Cursor (runs npx -y apiguru-mcp) |
| VS Code | Install in VS Code |
| Gemini CLI | gemini extensions install https://github.com/apiguru-app/agent-kit |
| Hermes, OpenClaw, any stdio client | npx -y apiguru-mcp (npm, Node only) or uvx apiguru-mcp (PyPI) |
| Skill only (any agent) | npx skills add apiguru-app/agent-kit or ClawHub apiguru-amazon-data |
The API is gated behind register → verify email → get key → top up. Every step assumes a human. Agents cannot do any of it, so agent traffic bounces off the front door.
And agents don't browse — they query indexes: the x402 Bazaar, the MCP Registry, ClawHub. Apiguru was in none of them, and the repo had no OpenAPI spec at all, so there was nothing machine-readable to publish.
Agents are the ones who find the defects in this API, so there are two ways back to us and neither costs anything:
POST https://dash.apiguru.app/api/v1/feedback with
{"message": "...", "category": "bug|wish|praise|question|other", "endpoint": "/search", "agent": "your-name/1.0", "contact": "optional"}.
No key, no signup, never billed. Read it at
https://dash.apiguru.app/feedback, or GET the same URL for JSON.send_feedback tool. From the skill:
python scripts/probe.py feedback --message "..." --category bug.This is not decoration. 1.1.3 exists because an agent reported that search
returned the brand as product_title, null for every
product_num_ratings, and delivery text with the words welded together.
| Path | What it is |
|---|---|
skill/apiguru-amazon-data/ | The agent skill: SKILL.md, references, and scripts/probe.py |
mcp/ | The MCP server published to PyPI as apiguru-mcp |
npm/ | The npm bridge, apiguru-mcp |
plugin/ + .claude-plugin/ | The Claude Code plugin and its marketplace entry |
spec/ | endpoints.json and the generated openapi.json / llms.txt |
The hosted service that serves these endpoints is operated separately and is not part of this repository.
See LICENSE.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx apiguru-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"app-apiguru-amazon-data": {
"command": "uvx",
"args": [
"apiguru-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceapiguru-mcppypiApiguru Amazon Data works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.