Skip to main content
MCP Directory
Reviews and loyalty Official SourceMedium integration

Judge.me MCP server

Checked September 2026.

Only the email side of Judge.me has a server. It reads campaigns, flows, subscribers, and analytics, and after a confirmation it can write email content, schedule or cancel a send, or switch a flow on or off. Product reviews, star ratings, and review requests stay behind the REST API and CSV export.

Judge.me MCP options

Every fact in a row comes from the publisher's own documentation.

Ways to reach Judge.me data from an assistant
Option Audience Reads or changes Sign-in Setup
Judge.me Email MCP Judge.me Merchants Covers Judge.me Email only: reads campaigns, flows, subscribers, and analytics, and can write email content, edit campaign details, schedule or cancel sends, and turn flows on or off, each after a confirmation; the MCP address in Settings under API tokens carries the token, and reviews are out of its reach. Can write API key or token Setup guide (opens in a new tab)
Judge.me data through SourceMedium's MCP https://mcp.sourcemedium.com/mcp SourceMedium Ours Merchants Reads Judge.me data from modeled SourceMedium tables, next to your other connected sources, with canonical metric definitions. Read only OAuth sign-in Setup guide

Connect Judge.me to your assistant

Each card lists the servers whose setup guide covers that assistant.

Connect Judge.me to ChatGPT or Claude

One MCP server per tool still can't answer a cross-channel question.

Each server brings its own sign-in, its own definition of revenue, and data your assistant can't join to the rest.

SourceMedium joins Judge.me with the rest of your store, ad, subscription, and returns data, keeps one set of maintained definitions, and gives ChatGPT, Claude, and other assistants a single connection to all of it.