Before you commit
Checked 2026-11-21- Community project (cosjef/keepa_MCP), not an official Keepa product — the MCP itself is free.
- You still need your own paid Keepa API subscription; installing the server does not include data access.
- Exhausted API tokens can return misleading empty results — check token status before trusting a blank answer.
- Worth it if you already pay for Keepa and want price-history questions answered inside Claude.
Details
What is Keepa MCP?
Keepa MCP is the community-maintained cosjef/keepa_MCP server. It exposes Keepa research tools to Claude through the Model Context Protocol: product lookup, price history, product discovery, deals and seller research.
It is not an official Keepa product, and installing it does not include a Keepa API subscription. It is most useful if you already use Keepa and want to explore Amazon product data conversationally.
Research note: reviewed against the project README on November 20, 2026. This is a documentation-based overview, not a hands-on benchmark. Example prompts below are suggestions, not measured results.
Before you install
| Requirement | What to prepare |
|---|---|
| Runtime | Node.js 18 or later, according to the project README |
| Client | Claude Desktop; follow your client's documentation for other MCP hosts |
| Data access | Your own paid Keepa API subscription and key |
| Local setup | A checkout of the repository and an absolute path to its built entry point |
| Security | Keep your API key in local client configuration; never paste it into a public issue or commit it |
How to connect Keepa MCP to Claude Desktop
- Clone the repository and open its directory.
- Run
npm install, thennpm run build, following the README. Review dependencies before running third-party code. - In Claude Desktop's MCP configuration, add a server with command
nodeand the absolute path todist/index.jsas its argument. - Set
KEEPA_API_KEYin that server's environment configuration. - Fully quit and reopen Claude Desktop, review the tool permissions, and start by checking token status.
Use the README configuration example for the complete JSON. Do not assume an npm package, Docker image or configuration for a different repository is interchangeable.
The README also documents optional KEEPA_RATE_LIMIT_DELAY and KEEPA_TIMEOUT settings. Check the current repository before changing defaults.
Useful Amazon research workflows
Check an ASIN before shortlisting it
Suggested prompt: “Look up this ASIN in the US marketplace and summarize its price history. Separate the returned data from your interpretation.”
The README lists keepa_product_lookup and keepa_price_history. Check the marketplace and time window before interpreting the output.
Compare a small product shortlist
Suggested prompt: “Compare these ASINs using the available Keepa data. Flag missing data instead of assuming zero demand.”
The project lists a batch lookup tool. Start with a small set of ASINs and inspect token use before expanding the batch.
Explore deals and competing sellers
The README lists product finder, deal search and seller lookup tools. Treat suggested opportunities as research leads: fees, shipping, returns, restrictions and margins still require separate checks.
Pricing and token limits
The repository lists an MIT license, but API access is separately paid to Keepa. The README states that endpoints consume different quantities of Keepa tokens and that history requests can cost more than basic lookups. Confirm current terms on the Keepa API page; no fixed monthly price is quoted here.
Keepa API tokens are separate from Claude model usage and any client subscription.
Limitations and troubleshooting
- Empty results can be misleading. The README warns that exhausted tokens may produce “No products found.” Check
keepa_token_statusbefore interpreting an empty search as a market finding. - Research estimates are not guaranteed sales. Verify how any velocity or inventory metric is calculated before using it for purchasing decisions.
- Tools missing in Claude? Check the absolute entry-point path, build output, JSON syntax and API key, then restart the client.
- Keep permissions narrow. These are research tools; the documented setup is not permission to change Amazon listings or place orders.
- Community maintenance matters. Review recent commits and issues before depending on the integration in a production workflow.
FAQ
Is Keepa MCP free?
The community repository is MIT-licensed. Keepa API access and your AI client may have separate charges.
Does Keepa MCP include a Keepa API key?
No. Supply your own KEEPA_API_KEY from Keepa. Do not share the key with other users.
Is this the official Keepa MCP server?
This page covers the community project cosjef/keepa_MCP, not an official Keepa integration.
Why does a Keepa search return no products?
It may be a genuine empty result, but the README also documents misleading empty results when API tokens are exhausted. Check token status and request settings first.
Related resources
Browse ecommerce MCP servers, compare Amazon seller tools, or use the seller calculators to evaluate costs that product research alone does not cover.