Judge.me MCP connector
The Judge.me connector brings product reviews, reviewers, review widgets and webhooks to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can find, summarize and update reviews inside their own Judge.me access with every action logged.
- OAuth or API key
- Free 14-day trial
- No credit card
Show me one star Judge.me reviews from this week
Working in Judge.me with Elaichi
-
List all Judge.me widgets product reviews
-
List all Judge.me widgets preview badges
-
List all Judge.me widgets featured carousels
How to connect Judge.me to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Judge.me MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Judge.me MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Judge.me MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Judge.me MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Judge.me MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Judge.me to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Judge.me through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Judge.me is logged.
-
Support
Find the reviews that need a reply
Ask for this week's one and two star Judge.me reviews, read what went wrong, and update each review before the shopper moves on.
-
Marketing
Pull quotes for a product launch
Ask for the five star reviews on the new range and get the lines worth quoting. Check which featured carousel and preview badge widgets are live so the quotes land on the store too.
-
Ecommerce
Check review counts and ratings by product
Ask how many reviews a product has and what its rating is, then compare against the rest of the catalog before deciding what to promote.
-
Merchandising
See which widgets each page shows
List the product reviews, reviews tab, verified badge and all reviews page widgets with their settings, without opening the theme editor.
-
Privacy
Handle a shopper's data request
When a shopper asks what Judge.me holds about them, look up the reviewer, correct a name or email, and file a data request in one go.
-
Growth
Know the moment a new review lands
Set up a Judge.me webhook so new reviews reach the team as they arrive, and list the existing webhooks to see what is already in place.
Try asking
- “Show me one star Judge.me reviews from this week”
- “Summarize what reviewers say about the linen shirt”
- “List the review widgets live on the store”
What connecting Judge.me gets you
6 screens from Elaichi, each doing one job for your Judge.me account.
Ask Elaichi to work across your apps.
Show me one star Judge.me reviews from this week
Summarize what reviewers say about the linen shirt
List the review widgets live on the store
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your reviews, get answers from Judge.me.
Plain questions come back with live Judge.me reviews, ratings and reviewer details.
Copy the endpoint
AI apps
Judge.me in Claude, ChatGPT, Cursor and Microsoft Copilot at once.
One governed endpoint, no SDK, no shared API key, connected once for everyone.
Tool catalog
34 Judge.me tools, no code to write.
Reviews, reviewers, widgets and webhooks, listed, read and updated from the catalog.
Toolboxes
Every team gets its own Judge.me toolbox.
Support handles reviews, marketing pulls quotes, each scoped to the tools it needs.
Shared connections
Teammates work in Judge.me without seeing the key.
One person connects Judge.me, shares it with teams, and the API key stays hidden.
Audit log
Every Judge.me change is written down.
When, who, what happened and which review, in a log nobody can edit.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Judge.me digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch reviews
Judge.me
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Judge.me
Queued
Automations
A schedule turns new reviews into a digest.
New Judge.me reviews are fetched, grouped, drafted, approved by a person, then posted back.
Judge.me health
Refreshed 4 minutes ago · every 15 minutes · from the reviews collection
Reviews
1,284 ↓ 12%
Reviewers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Reviews created
Last 14 days
By team
Share of activity
Support 34%
Marketing 27%
US store 21%
EU store 18%
Collections and dashboards
Review health, computed from Judge.me on schedule.
Reviews created over 14 days, ratings and counts by team, no model in the numbers.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Judge.me
All three can connect Judge.me to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Judge.me tools | Allow or restrict single Judge.me tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Judge.me call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Judge.me tools for your AI agents
34 tools are ready to call through Elaichi's MCP endpoint the moment you connect Judge.me, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Judge.me to Claude?
Connect Judge.me in Elaichi first, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Judge.me needs an app registered inside its own settings, so one person brings the client ID, secret and shop API key from Judge.me once, and that is the only time anyone types a credential. After that, each person signs in as themselves and Claude can work with reviews, reviewers and widgets.
Does Judge.me work with ChatGPT and Cursor as well as Claude?
Yes. Once Judge.me is connected in Elaichi, the same address, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Judge.me once and every client sees it.
What can an AI agent actually do with my Judge.me reviews?
It can find Judge.me reviews by product, rating or date, summarize what shoppers are saying, and update a review or a reviewer's details when something needs correcting. It can add a review a customer sent you directly, check review counts and ratings, show which widgets are live on the store and how they are set, and create a webhook so new reviews reach your team. Judge.me has many pieces, so short direct asks like one star reviews this week work better than long paragraphs.
Does connecting Judge.me give the AI every review and reviewer in my shop?
The agent only sees what the person who signed in can see in Judge.me. Elaichi can narrow that further, for example reading reviews but never touching reviewer details, and it can never grant more than Judge.me itself would. Access follows the person, not the connection.
Can I stop an agent from changing reviews in Judge.me?
Yes. Restrictions in Elaichi work per action, so you can allow reading Judge.me reviews and widgets while restricting updates to reviews or reviewers and the creation of webhooks. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Judge.me connection when someone leaves?
Offboarding that person in Elaichi ends their access to Judge.me through every client at once. A shared Judge.me connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Judge.me once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Judge.me MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Judge.me is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Judge.me?
Yes. Both let Claude, ChatGPT or Cursor use Judge.me. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Judge.me call.
How is Elaichi different from Composio for Judge.me?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Judge.me: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Judge.me in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot