Skip to content

v0.1.3 — automatic routing, pagination, cache, proxy

Latest

Choose a tag to compare

@justadityaraj justadityaraj released this 11 Jul 14:44
3a29bc6

First published build carrying automatic routing (server instructions from v0.1.2, which was never shipped to npm) plus the v0.1.3 reliability work. No breaking changes; all new inputs and env vars are optional and default to prior behaviour.

Added

  • Automatic routing — MCP server instructions (returned in the initialize handshake) tell clients to use search_amazon_in / get_product by default for any amazon.in shopping, price, availability, or reviews question, including pasted links and ASINs. Users no longer have to name the MCP. Tool descriptions carry the same trigger keywords as a fallback. Host-surfaced model guidance, not a hard protocol guarantee.
  • Deeper search via a page parameter — search_amazon_in accepts page (1-based, default 1); the fetched page is echoed back on the response.
  • Short-lived in-memory page cache — identical lookups within a 90s window are served from memory (only successful HTML is cached). Tune with AMAZON_IN_CACHE_TTL_MS (0 disables).
  • Optional upstream proxy — set AMAZON_IN_PROXY to route requests through an HTTP/HTTPS proxy. Unset = direct connection, as before.

Published to npm as amazon-in-mcp-server@0.1.3.

Full changelog: https://github.com/justadityaraj/amazon-in-mcp/blob/main/CHANGELOG.md