Judge.me MCP Server

Judge.me

Review management for e-commerce stores connected to Judge.me. Read product and shop reviews, or submit new web reviews when the store allows them.

Capability areas

• Review reads — list paginated reviews across the store or fetch one review by Judge.me internal id. Filter listings by reviewer id, internal product id, or star rating. Each review includes reviewer name and email, star rating, body text, product association, curation status, verification state, and timestamps.
• Review create — submit a web review (product-level or shop-level) when the store enables web reviews. Judge.me processes creates in the background like a storefront form submission.

Operational order

1. List recent reviews to discover internal review ids and spot rating trends.
2. Fetch individual reviews when you need full reviewer metadata or media flags for one row.
3. Create reviews only when the user explicitly wants to submit feedback — web reviews must be enabled on the store.

Workflows

• Review monitoring: list recent reviews and scan ratings for sentiment shifts.
• Feedback analysis: paginate through reviews filtered by product or rating.
• Social proof audit: check review volume and curation status before featuring on product pages.

Gotchas

• Create-only writes: Judge.me accepts review creates through the API but does not support updating or deleting reviews programmatically.
• Web review gate: create requests are ignored when the store disables web reviews.
• No verified flag on create: API-created reviews cannot be marked verified buyer status.
• Pagination: listing uses 1-based page numbers; per_page defaults to 100 (max 100).
• Store scope: each credential is bound to one Judge.me-connected shop; results are limited to that store.
• Product ids: listing filters use Judge.me internal product_id; create uses the platform external product id (for example Shopify product id).