What is the REP AI MCP server?

The REP AI MCP server connects your REP AI account to an AI assistant you already use, such as Claude. Once it's connected, you can ask how REP AI is performing, what shoppers ask about, where they get stuck and how support email was handled, and you can ask the assistant to fix a wrong answer. You approve every change in the chat.

What is MCP (Model Context Protocol)?

MCP, the Model Context Protocol, is an open standard that lets AI assistants connect to outside tools and data. An MCP server lists the tools it offers, and an assistant such as Claude calls them when a question needs them. The REP AI MCP server gives the assistant 13 tools for reading store data and suggesting changes to how REP AI answers shoppers.

What is the REP AI MCP server address?

The address is https://mcp.hellorep.ai/mcp/v1. It uses the Streamable HTTP transport and OAuth 2.1 sign-in with PKCE. You'll also find it, with the setup steps, in the REP AI Console under API > Connections (MCP).

How is the REP AI MCP server different from the REP AI shopping assistant?

The REP AI shopping assistant talks to your shoppers. It sells, answers questions and resolves support on your website and channels. The REP AI MCP server talks to you. It lets your own AI assistant read what REP AI sees and suggest fixes to how it answers. Both use the same REP AI account and data.

Is REP AI the same company as rep.ai?

No. REP AI's website is hellorep.ai and its MCP server runs at mcp.hellorep.ai. REP AI does not operate the rep.ai domain. To connect the right server, use the REP AI listing in the Claude Connectors Directory or the address https://mcp.hellorep.ai/mcp/v1.

Which AI assistants can connect to REP AI?

REP AI is listed in the Claude Connectors Directory, so it connects in a few clicks from Claude on web, desktop and mobile. Claude Code connects with one terminal command. Any other AI assistant that supports remote MCP servers with sign-in can connect with the address https://mcp.hellorep.ai/mcp/v1.

How do I connect REP AI to Claude?

In Claude, open Settings > Connectors, search for REP AI and click Connect. Sign in to the REP AI Console, pick your store, choose what Claude can see and change, and click Connect. Connectors added on claude.ai also work in the Claude desktop and mobile apps.

How do I connect REP AI to Claude Code?

Run claude mcp add --transport http rep-ai https://mcp.hellorep.ai/mcp/v1 in your terminal. Then run /mcp in Claude Code, select rep-ai and choose to authenticate. Your browser opens the REP AI sign-in page, where you choose permissions and click Connect. The Claude Code MCP documentation covers scopes and other options.

Who can connect an AI assistant to a REP AI store?

Only an admin of the store in REP AI can connect an assistant, approve its permissions or revoke it. Everyone on the store's team can see the list of connections. On a Claude Team or Enterprise plan, your organization owner may need to allow the REP AI connector first.

Is the REP AI MCP server included in my plan?

AI assistant connections are turned on per store plan. If you see "AI assistant connections are not on this store's plan" when you connect, email support@hellorep.ai and we'll help you turn them on.

Can Claude change my REP AI settings?

Only if you allow it, and only after you say yes to each change. Change permissions are off until a store admin turns them on. Claude suggests the smallest change, shows the text before and after, and applies it only after you approve it in the chat. Every change is saved in the Audit Log and can be reverted in one click.

What can an AI assistant never change in REP AI?

An AI assistant connected to REP AI can never delete anything, turn a skill on or off, or change triggers, targeting, chips, product links, refund or other action permissions, API endpoints, widget design, billing or integrations. You make those changes in the REP AI Console.

What shopper data can the assistant see?

Only what you allow. By default, the assistant sees store-wide performance and a summary of each conversation, not the messages. To read message text, it needs both The actual messages permission and the message-text switch. Shopper names, email addresses and phone numbers need the separate Who the shopper was permission.

Does REP AI send my data to the assistant all the time?

No. REP sends data only when the assistant asks for it to answer your question, and only within the permissions you approved. You can change those permissions or revoke the connection at any time in the REP AI Console.

Can a shopper's message tell the assistant what to do?

No. REP treats anything a shopper writes as information to report on. It is never an instruction to the assistant, and never your approval for a change.

How do I revoke an AI assistant's access to REP AI?

In the REP AI Console, open API > Connections (MCP) and click Revoke on the connection. The assistant loses access right away. A revoked connection can't be turned back on, so to connect again, start from the assistant and approve a new request.

How far back does REP AI MCP data go?

REP AI reports from the day your store started using REP AI. Topics and customer problems update once a day, so today's conversations show up tomorrow. Conversation search goes back one year, and looking up one shopper by email has no date limit.

Why are Claude's numbers slightly different from the REP AI Console?

The REP AI MCP server counts whole days in UTC. The REP AI Console may show your local time, so the first or last day of a period can be slightly different.

Why does the assistant say it can't answer a question?

The connection is missing the permission that question needs. For example, reading message text needs The actual messages, and looking up one shopper needs Who the shopper was. Click Edit on the connection in the REP AI Console, add the permission and ask again. You don't need to reconnect.

REP AI for developers

Connect your systems and AI agents to REP AI. Sync your catalog and orders, export conversations, read Sales and Support analytics and customer profiles, and connect AI assistants through the REP AI MCP server.

OpenAPI specOpenAPI 3.1, every endpoint, parameter and permission scope API catalogRFC 9727 list of every REP AI API MCP server13 tools for Claude, ChatGPT, Cursor and other assistants Help CenterSetup guides and product documentation

1. Get your credentials

Credentials are self-serve. Sign in to the REP AI Console and open API. No account yet? Start the 14-day free trial (no credit card).

Credential	Looks like	Use it for
API key	`rep_…`	Catalog, order events, privacy requests and conversations (`/external/v1/products`, `/events`, `/privacy`, `/conversations`). Send your `account_key` with each request.
Connection credential	`repmcp_…`	Analytics, Customers and the MCP server. You pick its permission scopes when you create it, and you can revoke it at any time.
OAuth 2.1 access token	issued by sign-in	The MCP server only. MCP clients sign in with OAuth 2.1 and PKCE, and the merchant approves the scopes.

Send every credential as Authorization: Bearer <credential>.

2. Quickstart

Read Sales Analytics

curl "https://api.hellorep.ai/external/v1/analytics/sales?from=2026-10-01&to=2026-10-31" \
  -H "Authorization: Bearer repmcp_YOUR_CREDENTIAL"

Find a shopper's conversations

curl "https://api.hellorep.ai/external/v1/conversations?account_key=YOUR_ACCOUNT_KEY&email=shopper@example.com" \
  -H "Authorization: Bearer rep_YOUR_API_KEY"

Connect an AI assistant over MCP

claude mcp add --transport http rep-ai https://mcp.hellorep.ai/mcp/v1

Then sign in when your client asks. The full parameters, request bodies and error codes are in the OpenAPI spec. Load it into Postman, Swagger UI or any OpenAPI tool.

3. APIs

API	Endpoints	Credential
Catalog	`POST/DELETE /external/v1/products`, `/product-groups`, `/discounts`, `POST /meta-fields`	API key
Order events	`POST /external/v1/events/order-completed`, `/order-status-update`	API key
Privacy	`POST /external/v1/privacy/customer-data-request`, `/customer-data-deletion`, `/store-data-deletion`	API key
Conversations	`GET /external/v1/conversations`, `/conversations/export`	API key
Analytics	`GET /external/v1/analytics/sales`, `/sales/skills`, `/support`, `/support/skills`, `/support/escalations-by-topic`, `/support/email-funnel`	Connection credential
Customers	`GET /external/v1/customers`, `/customers/details`	Connection credential with `customers.read`
MCP server	`POST https://mcp.hellorep.ai/mcp/v1` (Streamable HTTP, JSON-RPC 2.0)	Connection credential or OAuth token

Base URL: https://api.hellorep.ai. API index: GET /external/v1 (public).

4. Permission scopes

Connection credentials and OAuth tokens carry only the scopes the merchant grants. Request the least access your integration needs. Write scopes only propose changes; the merchant approves each one before it applies.

Scope	Grants
`analytics.read`	Store-wide performance, conversation topics and customer problems
`tickets.read`	Per-conversation metadata: topics, problem, sentiment, satisfaction, tags, orders. No message text.
`messages.read`	The messages between shoppers and REP
`customers.read`	Shopper name, email and phone
`support.read`	Support tickets REP handled and how they were resolved
`instructions.write`	Read, add and edit global AI instructions (no removal)
`faqs.write`	Read, add and edit custom FAQs (no deletion)
`skills.write`	Read and edit Sales and Support skill instructions

Machine-readable: RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata, plus the oauth2 security scheme in the OpenAPI spec.

5. Test before you go live

Every new account starts with a 14-day free trial, so you can build and test against a real store before you pay. To see how REP AI answers on any website first, use the free Simulator. Rate limits apply per credential and per store; a limited request gets 429 with a Retry-After header.

6. Help

Read the Help Center, or talk to our team about larger integrations.