> ## Documentation Index
> Fetch the complete documentation index at: https://juo.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Juo with an AI assistant

> Connect Claude or another AI assistant to your Juo store to look up subscriptions, review performance, and build workflows by asking.

Juo has an MCP server. MCP, the Model Context Protocol, is an open standard that lets an AI assistant work with the tools your business already runs on. Once your assistant is connected to Juo, you can ask about subscribers, subscriptions, and performance in plain language, and have the assistant make changes in your store.

Connected to Juo

*Illustrative conversations. Your assistant's wording will differ.*

## What you can ask

Ask in your own words. The assistant finds the right customer, subscription, or workflow in your store and shows what it did.

| Task | Example prompt |
| - | - |
| Find a customer | "Find [anna@example.com](mailto:anna@example.com) and show her active subscriptions." |
| Skip or move one order | "Skip Anna's next order." or "Move Anna's next order to November 20." |
| Change a subscription | "Pause Anna's subscription." or "Add a free sample to Anna's next order only." |
| Review performance | "Compare cancellations this month with last month." |
| Review workflows | "List my workflows and show how the cancellation flow performed last month." |
| Build a workflow | "Create a draft workflow that offers 15% off, then a pause, when a subscriber starts to cancel." |

The assistant can work with customers, subscriptions and their items and discounts, upcoming orders, products, workflows and workflow runs, and analytics. The [MCP reference](https://juo.dev/docs/mcp) lists every tool.

## Connect your assistant

You need a Juo account with access to the store you want to connect, and an assistant that supports MCP connectors. The server address is:

```text theme={null}
https://mcp.juo.com/mcp
```

> [tab] Claude
>
> 1. In Claude on the web or in Claude Desktop, open **Customize**, then **Connectors**.
> 2. Select **+**, then **Add custom connector**.
> 3. Enter the server address above and save.
> 4. The first time you use the connector, Claude opens the Juo login page. Log in with your Juo account, choose the store, and grant access.
>
> On Team and Enterprise plans, an organization owner adds the connector under **Organization settings**, then **Connectors**.

> [tab] Claude Code
>
> Add the server from your terminal:
>
> ```bash theme={null}
> claude mcp add --transport http juo https://mcp.juo.com/mcp
> ```
>
> In a Claude Code session, run `/mcp`, select `juo`, and log in with your Juo account.

> [tab] Codex
>
> Add the server, then log in. The login opens in your browser.
>
> ```bash theme={null}
> codex mcp add juo --url https://mcp.juo.com/mcp
> codex mcp login juo
> ```

> [tab] Cursor
>
> Add Juo to `~/.cursor/mcp.json` for all projects, or to `.cursor/mcp.json` for one project:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "juo": {
>       "url": "https://mcp.juo.com/mcp"
>     }
>   }
> }
> ```
>
> Cursor asks you to log in before the tools become available.

> [tab] Other assistants
>
> VS Code, Windsurf, Zed, Continue, and assistants that only support local servers each have their own setup. The [MCP reference](https://juo.dev/docs/mcp) has the configuration for each.

Once connected, start with a question that only reads data:

> List my workflows and show which ones are published.

## Stay in control

The assistant works with your live store, so treat its actions as you would a teammate's.

* **One store per connection.** Access is limited to the store you choose at login. To work with another store, connect again and choose that store.
* **Changes are real.** Pausing, skipping, and cancelling affect real subscribers, and cancelling can email the customer. Review each action before your assistant runs it, and keep approval prompts on for anything that changes data.
* **Deleting needs extra care.** Deleting a customer or a product is permanent. Workflows are never deleted through MCP: removing one archives it, and the run history stays.
* **Workflows are saved as drafts.** The assistant asks before it publishes. Pop-ups, polls, and other customer-facing content can't be previewed through MCP, so open the draft in the [workflow editor](https://juo.io/docs/workflows/workflows-overview.md) and check it before you publish.
* **Disconnect when you no longer need it.** Remove the Juo connector in your assistant's settings.

## Start from a guide

The [cancellation flow guide](https://juo.io/docs/workflows/guides/cancellation-flow.md) describes the goal and the flow of a proven pattern, so it works as a brief. Share it with your assistant and ask for a draft:

> Using the cancellation flow guide, create a draft workflow in my store. Offer a discount first, then a pause.

Review the draft in the editor, adjust the offers, and publish when it matches your terms.

## For developers and advanced setups

> [card] [MCP reference](https://juo.dev/docs/mcp)
>
> Every tool, the full list of supported clients, and endpoint details.

> [card] [Connect with an API key](https://juo.dev/docs/mcp#connecting-with-an-admin-api-key)
>
> Use an Admin API key for scripts, scheduled tasks, CI, and self-hosted agents.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.