Claude

Set up in Settings → Connectors in Claude, or claude mcp add

Evident runs a remote MCP server, so Claude can work with your store’s evidence directly — no plugin to install and no client to write.

https://mcp.evidentugc.com/mcp

Connecting in Claude

Claude’s connector settings have no field for an API key, and none is needed — you sign in to Evident instead.

1. In Claude, go to Settings → Connectors and add a custom connector.
2. Enter the URL above. Leave the OAuth client ID and secret fields empty; Claude registers itself with Evident automatically.
3. Click Connect. You’ll be asked to sign in to Evident and to choose an organization. Claude is scoped to that organization for the life of the connection.

Claude then acts as you, with your role in that organization, and Evident re-checks your membership on every call. Remove yourself from the organization and the connection stops working. To point Claude at a different organization, disconnect and reconnect.

Connecting in Claude Code

Claude Code takes a bearer token directly, so an API key works there:

claude mcp add --transport http evident https://mcp.evidentugc.com/mcp \
  --header "Authorization: Bearer evnt_…"

Create the key in Evident under Settings → API Keys. Start with one scoped read. The key carries its organization, role and scopes — Claude Code can do exactly what that key can do and nothing more.

What it can do

Read — list_stores, search_products, get_product, list_orders, get_customer_activity, search_reviews, get_review, get_product_review_stats, get_review_analytics, get_top_products_by_reviews, get_evidence_analytics, list_faqs, get_loyalty_account, get_loyalty_stats, list_loyalty_rewards

Write — moderate_review, reply_to_review, send_review_request, create_faq, update_faq, adjust_loyalty_points, create_loyalty_reward

Read tools are annotated read-only, so Claude can show you which calls actually change something.

Things worth asking

Which products dropped below 4 stars this quarter, and what are the negative reviews complaining about?

Find reviews below 3 stars from the last month with no reply, and draft a reply for each.

Read our FAQs and the last 200 reviews for this product. What are customers repeatedly asking that we haven’t answered?

What has [email protected] bought, reviewed, and what’s their loyalty balance?

Summarise the pending moderation queue and flag anything with personal data or a safety concern.

Which store

Most tools take a store environment ID. list_stores is how Claude finds it, and it works even with a narrowly scoped key — otherwise a scoped key could not discover the store it is scoped for.

If you run several stores, say which one you mean.

Before you give it write access

adjust_loyalty_points mints value. Points redeem into store credit and discount codes. It is genuinely useful — crediting a customer after a damaged order is a good use of an assistant — and it is the one tool whose mistakes cost money. On an API key, omit loyalty:write if you are not sure. A signed-in connection carries your own role, so if you can adjust points in Evident, Claude can too.

Review content is untrusted text written by the public. Anyone can leave a review, so anyone can put text in front of your model. Have Claude draft replies rather than post them, and do not build unattended automation that acts on review bodies.

Notes

• A signed-in connection is recorded in the activity log as an MCP session for your user. An API key is recorded as the key — so use one key per assistant, not one shared key.
• Key creation and first use are recorded in the security audit log.
• Loyalty tools return nothing useful for Shopify stores today: points are earned on BigCommerce orders only.

See Agent access and Automating with AI agents.