judgeme_widget_ all_ reviews_ countGet the single total number of product plus shop reviews for the store.
Read and moderate reviews, post public or private replies, queue review-request emails, and pull the widget HTML your product pages render — all scoped to the one store you connect.
PopMCPJudge.me
Every read, write and trigger in the connection: reviews, replies, orders, line items, products, reviewers, webhooks, shop settings and widget HTML.
52 tools in the full catalog: 33 read and 19 write. 30 load by default, and the rest are found with tool search.
judgeme_widget_ all_ reviews_ countGet the single total number of product plus shop reviews for the store.
judgeme_widget_ all_ reviews_ ratingGet the single average rating across all product and shop reviews for the store.
judgeme_widget_ preview_ badgeGet the Preview Badge HTML for one product: its star rating plus review count, the small badge shown under a product title or on collection cards.
judgeme_widget_ product_ reviewGet the ready-to-embed Review Widget HTML for one product — the full list of that product's reviews as shown at the bottom of a product page.
judgeme_widget_ settingsGet the store's widget styling as an HTML fragment containing a <script> and a <style> tag — the colors, text, and layout choices made in the Judge.me admin.
judgeme_find_ orderResolve ONE order from its EXTERNAL (Shopify) order id and get back the Judge.me internal order id plus its fulfilment state.
judgeme_get_ orderGet one order by its Judge.me INTERNAL order id.
judgeme_list_ delivery_ trackingsList delivery trackings (Judge.me's name for order fulfilments).
judgeme_list_ line_ itemsList order line items — the per-product rows Judge.me schedules individual review requests from.
judgeme_list_ ordersList the orders Judge.me holds for the store — these are what drive automatic review-request emails.
judgeme_count_ reviewsCount reviews without fetching them.
judgeme_create_ private_ replyEmail a PRIVATE reply to the reviewer.
judgeme_create_ replyPost a PUBLIC store reply under a review.
judgeme_create_ reviewCreate a review for the connected store, exactly as if a shopper had submitted the public review form.
judgeme_get_ reviewGet one review by its Judge.me INTERNAL review id.
judgeme_list_ reviewsList reviews for the connected store, newest first.
judgeme_publish_ or_ hide_ reviewPublish or hide an existing review on the storefront.
judgeme_create_ webhookSubscribe a URL to a Judge.me event.
judgeme_delete_ webhookUnsubscribe a webhook.
judgeme_list_ webhooksList the webhooks registered for this store.
judgeme_find_ productResolve ONE product from its Shopify id or its storefront handle, and get back the Judge.me INTERNAL product id.
judgeme_find_ reviewerLook up ONE reviewer by email address or by EXTERNAL (Shopify) customer id, and get back their Judge.me internal reviewer id.
judgeme_get_ productGet one product by its Judge.me INTERNAL product id.
judgeme_get_ reviewerGet one reviewer by Judge.me INTERNAL reviewer id — name, email, phone, tags, and marketing-consent state.
judgeme_get_ shopGet the connected store's Judge.me profile: { shop: { id, name, domain, custom_domain, platform (shopify | woocommerce | bigcommerce | ...), plan, awesome (true on a paid Awesome plan), owner, email, phone, country, currency, timezone, widget_version, dmarc_ok, onboarding_progress, created_at, updated_at } }.
judgeme_list_ productsList the store's products as Judge.me knows them.
judgeme_list_ reviewersList the store's reviewers (the customer records behind reviews).
judgeme_list_ settingsRead the store's Judge.me configuration values by key — useful to check what is switched on before acting, e.g. whether web reviews are enabled (judgeme_create_review silently does nothing when they are not), how many wait days apply before a review request is sent, or which review-request emails are active.
judgeme_upsert_ reviewerCreate or update a reviewer record.
judgeme_send_ review_ requestManually queue a review-request email to one customer for one product — the tool to reach for when someone asks to "ask this buyer for a review".
judgeme_widget_ all_ reviews_ pageGet the All Reviews Page HTML — the dedicated page showing every product and store review in one place.
judgeme_widget_ checkout_ commentsGet the Checkout Comments widget HTML for one product.
judgeme_widget_ featured_ carouselGet the Reviews Carousel HTML — the rotating strip of reviews the store has featured, normally placed on the homepage.
judgeme_widget_ html_ miracleGet Judge.me's "Miracle HTML": a fragment that renders the essential parts of the widgets before the widget JS and CSS have loaded, so ratings are visible immediately and do not pop in.
judgeme_widget_ reviews_ tabGet the Floating Reviews Tab HTML — the floating button that opens all product and store reviews from any page.
judgeme_widget_ shop_ reviews_ countGet the total number of SHOP-level reviews (reviews about the store itself rather than a product).
judgeme_widget_ shop_ reviews_ ratingGet the average rating of SHOP-level reviews (reviews about the store itself).
judgeme_widget_ verified_ badgeGet the Verified Reviews Count Badge HTML — the trust badge showing how many verified published reviews the store has.
judgeme_create_ orderPush an order into Judge.me so it can schedule review-request emails for the items bought.
judgeme_get_ delivery_ trackingGet one delivery tracking (fulfilment) by its Judge.me internal id, with its courier, tracking number, and current tracking status.
judgeme_get_ line_ itemGet one order line item by its Judge.me internal line-item id, including whether it has produced a review yet (`review_id`) and when its review request is scheduled.
judgeme_update_ delivery_ trackingCorrect the courier or tracking number on a delivery tracking, so Judge.me can follow the parcel and time the review request to arrival.
judgeme_update_ orderUpdate an order Judge.me already holds — the usual reason is to cancel it (set cancelled_at) so pending review-request emails stop, or to correct the customer's details or locale.
judgeme_bulk_ create_ webhooksRegister several webhook subscriptions in one call — the efficient way to wire up a new integration that needs both review events plus a few widget events.
judgeme_get_ webhookGet one webhook subscription by its Judge.me internal webhook id.
judgeme_update_ webhookChange the event key or destination url of an existing webhook subscription.
judgeme_create_ checkout_ commentCreate a checkout comment — a short note a buyer leaves on the order-confirmation page.
judgeme_create_ productRegister a product in Judge.me.
judgeme_request_ reviewer_ dataRaise a GDPR/CCPA data-access request for one customer, listing the orders whose data they asked for.
judgeme_uninstall_ shopDESTRUCTIVE AND IRREVERSIBLE: uninstalls the entire store from Judge.me.
judgeme_update_ productReplace a product's details in Judge.me.
judgeme_update_ shopUpdate the store's Judge.me profile — contact email, owner name, phone, storefront domain, country, timezone.
Credentials off one Judge.me screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
Paste your Shop domain and Private API token — both sit on one Judge.me screen: Settings, then Integrations, then View API tokens at the top right. No OAuth app, client secret or redirect URL. One store per connection.
example.myshopify.com••••••••••••3f7aOnly clients you tick on the PopMCP consent screen reach Judge.me, and for those, hiding a live review, posting a public reply or emailing a customer happens as soon as the AI calls it. The Free plan is read-only, and tools beyond the default set stay searchable.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Judge.me credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Give me the store's overall rating and review count, then the newest one-star reviews
judgeme_widget_all_reviews_countok
Then just ask for the work
“Give me the store's overall rating and review count, then the newest one-star reviews”
“Hide every one-star review about late shipping and private-message those reviewers”
“Ask the buyer of order 10482 to review the mug they bought”
“Did whoever left yesterday's one-star review ever order from us before?”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Judge.me behind an AI client.
Sign in to Judge.me, go to Settings, open Integrations, then click View API tokens at the top right — both values sit on that one screen. There is no OAuth app, client secret or redirect URL to create anywhere. The connection is locked to the single store those credentials belong to.
Judge.me keeps its own ids, and get_review, get_order, get_product and get_reviewer all expect the internal one — this is the thing that trips people up first. That is what the resolvers are for: find_order takes the external Shopify order id and hands back the internal id plus fulfilment state, find_product takes a Shopify id or a storefront handle, and find_reviewer takes an email address or external Shopify customer id. In practice the agent chains a find call before a get call, so you can ask using the id you actually have.
Yes. publish_or_hide_review flips a review's visibility on the storefront, create_reply posts a public store reply under a review, and create_private_reply emails the reviewer directly. Those are writes and run as soon as the AI calls them, so tick Judge.me on the consent screen only for clients that should post, and ask for the wording in chat first if a human should read it before a shopper does.
send_review_request queues one review-request email to one customer for one product — the manual version of what Judge.me normally automates. create_order pushes an order in so Judge.me can schedule requests for the items bought, while list_orders and list_line_items show what those automatic emails are working from. There is also an "Item awaiting a review" trigger for an ordered item that still has no review after its request went out.
Widgets is the largest module in this connection. widget_product_review returns the full review list HTML for one product, widget_all_reviews_page the dedicated all-reviews page, widget_featured_carousel the rotating strip of featured reviews, and widget_preview_badge and widget_verified_badge the small star and trust badges. widget_settings returns your admin styling as a script and style fragment, and widget_html_miracle the pre-load fragment that stops ratings popping in.
get_shop returns the store's Judge.me profile, including the platform it runs on — shopify, woocommerce, bigcommerce and others — plus plan, owner, currency, timezone, widget version and DMARC state. The resolver tools are built around external Shopify ids and storefront handles, though find_reviewer also accepts a plain email address. list_settings reads your Judge.me configuration values by key, which is worth checking before an agent acts on anything.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Judge.me in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Judge.me on the consent screen. The Judge.me tools are then available in that session, and no Judge.me credential is stored on your machine.
Loading 52 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 30-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 52 here. A trigger is something PopMCP watches for you: 11 Judge.me events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Judge.me.
Launch a hosted MCP endpoint for Judge.me, keep tool access under control, and start testing real workflow prompts right away.