Is this an official Judge.me MCP server?

No. It is Memtro's MCP server with Memtro's Judge.me connector behind it: the connector reads Judge.me through its API with the credentials you connect on Dashboard → Connections, and Judge.me publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Judge.me?

Only when you ask, and only what it has been granted: post a public reply to a review (the reviewer is emailed only if asked); publish a review on the storefront, or hide (archive) it; email a reviewer a private reply about their review. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Social and reputation

Judge.me MCP server

Judge.me in any MCP client, through Memtro: Judge.me does not publish this server. Memtro's Judge.me connector reads Judge.me through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Judge.me product reviews for a Shopify store: reviews by rating, product or reviewer with the text, product, reviewer's name, verification and moderation state, and the rating breakdown of what was read. Can post a public reply to a review, publish or hide a review, and email a reviewer a private reply.

Reads

judgeme_reviewsJudge.me product and store reviews: rating, title and text (cut short), product, reviewer's name, source, verification and moderation state…
judgeme_reviewOne Judge.me review in full by its Judge.me id: rating, title, the whole text, product, reviewer's name and state.

Acts, when you ask

These change something in Judge.me. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

judgeme_reply_to_reviewPost a public reply from the store to a Judge.me review.
judgeme_publish_or_hide_reviewPublish a Judge.me review on the storefront, or hide it (archive it, so it is never shown).
judgeme_send_private_replyEmail the reviewer a private reply about their Judge.me review, from the store.

Connect it

First connect Judge.me on Dashboard → Connections, then add Memtro to your client once. The Judge.me tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Judge.me connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Show this week's 1-star reviews.
› What are people saying about the oak table?
› What is the average rating in the reviews of the walnut shelf?
› Which of the latest 5-star reviews are verified?
› Reply to review 48213 that a replacement leg is on its way.

Questions

Is this an official Judge.me MCP server?: No. It is Memtro's MCP server with Memtro's Judge.me connector behind it: the connector reads Judge.me through its API with the credentials you connect on Dashboard → Connections, and Judge.me publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Judge.me?: Only when you ask, and only what it has been granted: post a public reply to a review (the reviewer is emailed only if asked); publish a review on the storefront, or hide (archive) it; email a reviewer a private reply about their review. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.