Ordergroove MCP

Ordergroove MCP connects the AI tool your team already uses, like Claude, to your Ordergroove data. Ask about your subscription program in plain language and get answers, tables, and charts back, or find out exactly what happened with a specific order or subscription. This article covers what Ordergroove MCP is, what data it can access, how to set it up, how to troubleshoot common issues, and how your data stays secure. For sample prompts and tips, see Ordergroove MCP: Sample Prompts and Best Practices.

What is Ordergroove MCP?

MCP stands for Model Context Protocol, an open standard for connecting AI clients, like Claude, ChatGPT, or Microsoft Copilot, to outside data and tools. Ordergroove MCP is a secure, read-only connection between your AI client and your Ordergroove data. Once it's connected, your AI client can pull the Ordergroove data it needs to answer your questions, live, whenever you ask.

This is the "bring your own AI" path: your team keeps using the AI tool it already prefers, now with your Ordergroove data available right inside it.

Ordergroove MCP isn't an AI model. It doesn't generate answers or analysis on its own—your AI client does that, using the data the connector returns. Which AI model works with your data depends on the AI client your organization chooses.

What can you do with it?

• Get answers without opening a dashboard. Ask about revenue, orders, subscriptions, and subscribers, broken down by product, frequency, or subscription type, and compared with any earlier period.
• Automate recurring reports. Turn the KPI summary you build by hand each week into a single prompt, then pair it with your AI client's scheduling tools to have it delivered automatically.
• Plan around inventory. See how many active subscriptions and upcoming orders include a product before it runs out of stock or is discontinued.
• Resolve support issues faster. Find out why an order failed or a subscription wasn't created, using order details and system logs, without escalating or digging across systems.
• Combine Ordergroove with your other tools. If your AI client is also connected to other sources, like your ecommerce platform, inventory system, or data warehouse, it can bring that data together with Ordergroove's to answer broader questions.

How is this different from the Ordergroove API?

Ordergroove MCP is built on Ordergroove's existing APIs and works with data Ordergroove already holds. The difference is that you don't need a developer: you ask in plain language, and your AI client chooses the right lookups, combines the results, and explains them. It also includes recurring order and subscription creation logs for troubleshooting.

What data can you access?

Ordergroove MCP gives your AI client a fixed set of read-only lookups in three areas. Your AI client picks the ones it needs based on your question and can combine several to answer it. What you can see is also limited by your Ordergroove permissions (see Permissions and access below).

Program analytics

Aggregate metrics for any date range, by day, week, month, or year, and compared with the previous period, the same period last year, or dates you choose.

Revenue is reported in your store's primary currency.

Individual records

Look up or search specific records, useful for support questions and spot checks:

• Subscriptions: product, frequency, quantity, price, status, start and cancellation dates, cancel reason, next order date, upcoming skips, and prepaid or free trial details.
• Orders: status, placement date, items, totals and discounts, number of placement attempts, and rejection messages.
• Customers, products, and offers: customer records, your product catalog (including bundles and related products), and the offers and incentives set up in your program.

You can search by customer, subscription, product, order status, or order placement date.

Troubleshooting data

• Recurring order logs: system activity for a specific recurring order, showing why it succeeded, failed, or was retried.
• Subscription creation logs: system activity from checkout, showing why a subscription was or wasn't created.
• Shopify data (Shopify merchants only): billing attempts, subscription contracts, orders, customers, and product variants from Shopify, so you can see what each system recorded.

Not available yet

Ordergroove MCP doesn't currently support:

• Making changes of any kind—it's read-only.
• Cancellation-reason reporting across your program. (You can see the cancel reason on an individual subscription.)
• Cohort, retention-curve, or lifetime value (LTV) analysis.
• History of customer actions, like skips, swaps, and frequency changes.
• Raw data exports.
• Customer personal information, like names, email addresses, phone numbers, and street addresses.

We plan to expand the data available over time. If you ask about one of these areas, your AI client may try to piece together an answer from partial data, so treat the result as an estimate.

Permissions and access

Ordergroove MCP mirrors your Ordergroove Admin permissions one-to-one. You sign in with your own Ordergroove login, and the connector can only see what that login can see. If you have access to something in the Ordergroove Admin, you can ask about it through the connector; if you don't, the connector can't reach it either. For example, analytics answers require access to Analytics in the Ordergroove Admin.

This works the same in every AI client, including ChatGPT and Slackbot: each person signs in with their own Ordergroove login and sees only what that login allows.

The API access permission

Pulling data in bulk, like searching or listing orders, subscriptions, or customers, also requires the API access permission on your Ordergroove user. This permission isn't turned on for new users by default, and Ordergroove can only add it with approval from your company's Ordergroove admin.

If your AI client reports a permissions error or mentions API access:

1. Ask your company's Ordergroove admin to request the API access permission for your user.
2. Your admin contacts your Customer Success Manager (CSM) or Ordergroove Support to approve the request.
3. Once the permission is added, try your question again. If you still see the error, disconnect and reconnect the connector.

Setting up Ordergroove MCP

Ordergroove MCP is built on the open MCP standard, so it isn't limited to Claude. Setup only needs to happen once per person, and each person signs in with their own Ordergroove login. Find your AI client in the table below, then follow its steps.

Before you start

You'll need:

• An Ordergroove Admin login for each person who will use the connector. If your team already signs in to the Ordergroove Admin, you're set. Otherwise, ask your company's Ordergroove admin to add you.
• The right Ordergroove permissions for the data you want to ask about. See Permissions and access above.

Claude

Setup takes a few minutes. You'll need a Claude account. Custom connectors are available on every Claude plan, though the Free plan is limited to one custom connector.

You'll use these connection details:

Note: The Client ID isn't a password. It's safe to store and share.

On a Team or Enterprise plan, an organization Owner does this once:

1. In Claude, go to Organization settings > Connectors and click Add.
2. Hover over Custom and select Web.
3. Enter a name, like Ordergroove, and enter https://mcp.ordergroove.com/mcp as the server URL.
4. Click Advanced settings and paste the OAuth Client ID from the table above. Leave Client Secret empty.
5. Click Add.

Each team member then goes to Customize > Connectors, finds the Ordergroove connector (labeled Custom), and clicks Connect to sign in with their own Ordergroove login.

On a Free, Pro, or Max plan, each person adds the connector themselves:

1. In Claude, go to Customize > Connectors, click +, and select Add custom connector.
2. Enter a name, like Ordergroove, and enter https://mcp.ordergroove.com/mcp as the server URL.
3. Click Advanced settings and paste the OAuth Client ID. Leave Client Secret empty.
4. Click Add, then Connect.

Clicking Connect opens the Ordergroove sign-in page. Sign in the same way you sign in to the Ordergroove Admin (if you access Ordergroove through Shopify, you'll sign in with Shopify), then approve the consent screen. This authorizes the connector for your Ordergroove data, and only your data. Claude never sees your password.

Once you're connected, open a Claude chat, click + in the lower left, select Connectors, and make sure the Ordergroove connector is turned on. Then try a question like:

"Using Ordergroove, how did my total subscription revenue last month compare with the month before? Split it into first-time and recurring revenue."

Claude may ask for your permission before it uses an Ordergroove tool. You can allow it for that one request or always.

For more prompts organized by use case, plus tips for getting accurate answers, see Ordergroove MCP: Sample Prompts and Best Practices.

ChatGPT

Ordergroove is listed in ChatGPT as an official plugin. While signed in to ChatGPT, open the Ordergroove plugin listing, connect it, and sign in with your Ordergroove login when prompted. Depending on your ChatGPT plan, a workspace admin may need to allow the plugin first.

Slackbot

Slackbot connects to MCP servers through a Slack app, so setup has two parts. First, someone who can create and install Slack apps for your workspace adds Ordergroove MCP to a Slack app. These steps follow Slack's guide, Connecting an MCP server to the Slackbot MCP Client.

1. Go to api.slack.com/apps and open the Slack app you want to use, or click Create New App to make one.
2. In the left sidebar, under Features, click MCP Servers, then click Get Started.
3. Fill in the form with the values in the table below. Leave any other fields as they are.
4. Click Save.
5. Install the app to your workspace: go to OAuth & Permissions and click Install to Workspace (or Install to Organization on an Enterprise organization). If the app was already installed, reinstall it so it picks up the new MCP permission. Depending on your workspace settings, a Slack admin may need to approve the install.

Note: Slackbot uses its own Client ID, which is different from the one in the Claude section. Copy each value exactly, including the full Authorization URL.

Then each person connects their own Ordergroove login:

1. Open a DM with Slackbot.
2. Click the Apps button in the Slackbot toolbar.
3. Click + next to the Slack app your team set up.
4. When you're redirected to the Ordergroove sign-in page, sign in the same way you sign in to the Ordergroove Admin, then approve the consent screen.

Once connected, you can ask Slackbot about your Ordergroove data. Slackbot asks your permission before each Ordergroove tool call; choose Allow once or Always allow. Slackbot stops any request that takes longer than 60 seconds, so if a question times out, try a shorter date range or a narrower question.

Other AI clients

Other AI clients that support custom (remote) MCP servers with OAuth sign-in may also be able to connect, though setup in those tools is more involved, changes often, and usually needs an admin or developer on your team.

• Microsoft Copilot: Microsoft offers several Copilot products, and MCP support depends on which one your organization uses. Connections are typically set up by an admin or developer, for example as a tool in Copilot Studio. See Microsoft's guide to connecting an existing MCP server.
• Google Gemini: Custom MCP servers are connected by an administrator in Gemini Enterprise, through your Google Cloud environment. See Google's guide to setting up a custom MCP server.
• Other clients: Look for a setting that adds a remote MCP server by URL with OAuth sign-in, then use the connection details in the Claude steps above.

For Microsoft Copilot, Google Gemini, and other clients, Ordergroove's sign-in requires our OAuth Client ID, and some AI clients also need Ordergroove to approve their sign-in redirect URL. Reach out to your CSM or Ordergroove Support before you start, and we'll work through setup with you and your developer.

Troubleshooting

I see "auto registration is not supported"

The connector was added without the OAuth Client ID, so Claude tried to register itself automatically, which Ordergroove's server doesn't allow. Claude doesn't support editing a custom connector, so remove the connector and add it again, this time pasting the OAuth Client ID under Advanced settings.

I can't find the Ordergroove connector in Claude

On a Team or Enterprise plan, an organization Owner needs to add the connector first. Once they have, you'll find it in Customize > Connectors with a Custom label.

I can't sign in

Use the same login you use for the Ordergroove Admin. If you can't sign in to the Ordergroove Admin either, ask your company's Ordergroove admin for access.

My connection stopped working, or I'm asked to sign in again

This is expected. For security, sign-ins last about 7 days without use, and up to 30 days with regular use. If you sign in through Shopify, Shopify data needs a fresh sign-in every 24 hours. To reconnect, go to Customize > Connectors, select the Ordergroove connector, and click Connect.

My AI client says I don't have permission or API access

Your Ordergroove user doesn't have access to that data yet. See Permissions and access above for how to request it.

Claude answers without using Ordergroove

Make sure the connector is turned on for the conversation (+ > Connectors), and mention Ordergroove in your question. If other data sources are connected, Claude may use one of those instead.

The numbers look wrong or don't match my Ordergroove dashboard

This usually means your AI client interpreted your question differently than you meant. For common causes and how to check an answer, see When the numbers look wrong in Ordergroove MCP: Sample Prompts and Best Practices.

My AI client isn't Claude, and it can't connect

Your AI client may not support custom MCP servers, or it may need extra setup on our side. See Other AI clients under Setting up Ordergroove MCP above, and contact your CSM or Ordergroove Support for help.

Data and security

Here's how Ordergroove MCP handles your data. If your security team needs more detail for a vendor review, contact your CSM for our MCP security and architecture overview.

• Only your data. Each connection is scoped to the Ordergroove account you sign in with. Your questions can't reach any other merchant's data.
• Read-only. Your AI client can read and analyze your data but can't create, change, or delete anything in your program. If write capabilities are added in the future, they'll require explicit permissioning, and more granular per-user controls are planned alongside them.
• Permissions follow your Ordergroove roles. The connector mirrors each person's existing Ordergroove Admin permissions, nothing more.
• No customer PII in responses. Customer names, email addresses, phone numbers, and street addresses are left out of every response, and system logs are scanned and redacted before they're returned. Payment details are limited to items like card brand and expiration date. Ordergroove doesn't store full card numbers or security codes, so they can never be returned.
• Live data, no extra copies. The connector fetches data from Ordergroove's existing systems at the moment your AI client asks for it. It doesn't keep its own copy of your data, and it doesn't collect any new data.
• Secure sign-in. Authentication uses OAuth 2.1 with PKCE, the standard the MCP specification is built on. You sign in directly with Ordergroove (or Shopify), and your AI client never sees your password.
• No network changes needed. Requests come from your AI provider's cloud (for Claude, Anthropic's servers), not your company network, so there are no firewall or allowlist changes to make.
• Usage limits. Ordergroove's standard API limits apply, and lists are returned in batches to keep the platform stable for everyone.

Does Ordergroove MCP use AI to process our data?

No. Ordergroove MCP is a data connection, not an AI model. The analysis happens in the AI client you choose, under your organization's agreement with that provider. Ordergroove doesn't see your prompts or your AI client's answers, only the specific data requests your AI client makes, like a date range or an order ID. How your AI provider stores or uses your conversations, including whether they're used for model training, depends on your plan and agreement with them, so review their data policies.

How do we turn off access?

Anyone can disconnect the connector in their AI client at any time. On a Claude Team or Enterprise plan, Owners can remove it for the whole organization in Organization settings > Connectors. Removing a person's Ordergroove Admin access (or, if they sign in through Shopify, their access to the Ordergroove app in Shopify) also ends their connector access.

Additional reading

• Ordergroove MCP: Sample Prompts and Best Practices — ready-to-use prompts by use case, tips for accurate answers, and what to do when the numbers look wrong.
• Ordergroove Agents — an overview of agents, how they differ from "just AI," and the full agent lineup.
• Analytics Agent — ask questions and get insights from your program data; today it runs through this connector.
• Payment Agent — how the Payment Agent recovers revenue from failed payments.
• Retention Agent — how the Retention Agent spots subscriber drop-off and builds workflows for your approval.