> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.claruswms.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Claude to Clarus
> Add Clarus as a custom connector in Claude — for your own account or your whole organisation — so you can work with your warehouse data using your own Clarus login.
Add Clarus to Claude as a **custom connector**, then ask Claude about your warehouse — and have it make changes — in plain English. Setup takes a minute and uses your normal Clarus sign-in.
**AI accuracy:** AI-generated responses can sometimes be inaccurate, incomplete, or misleading. Always verify the assistant's output before acting on it — especially for stock movements, order changes, or any actions that affect your live warehouse data. The assistant is a tool to help you, not a replacement for your own judgement.
Before you start, have your connection address ready:
```text theme={null}
https://agents.claruswms.ai/mcp/{subdomain}
```
Replace `{subdomain}` with your Clarus subdomain. See [Connect AI assistants to Clarus](/knowledgebase/integrations/ai-assistants-overview) if you're unsure what yours is.
Custom connectors are a Claude feature (currently in beta) available on plans that support them — Pro, Max, Team, and Enterprise. Menu names can vary between Claude versions.
## Add the connector
In Claude, go to **Customize → Connectors**. (You can also open the **+** menu in a chat, choose **Connectors**, then **Manage connectors**.)
Click the **+** next to Connectors, then choose **Add custom connector**.
In the dialog, give it a name like `Clarus` and paste your connection address (`https://agents.claruswms.ai/mcp/{subdomain}`). Under **Advanced settings**, leave **OAuth Client ID** and **OAuth Client Secret** **blank** — Clarus handles sign-in for you. Then click **Add**.
Claude opens a Clarus sign-in window — sign in with your Clarus username and password and **approve** access.
Start a new chat, make sure the **Clarus** connector is enabled (via the **+** menu), and ask a question such as "How many units of `WIDGET-RED-500` are in stock?"
An organisation owner adds Clarus once for the team. It's then available to everyone, but each person still signs in with their **own** Clarus account — so they only see and do what their account allows.
An organisation **Owner** goes to **Organization settings → Connectors**.
Click **+ Add**, choose **Custom**, then choose **Web** (Clarus is a hosted server, so it's a Web connector — not Desktop).
In the **Add custom connector** dialog:
* **Name:** `Clarus`
* **URL:** your connection address (`https://agents.claruswms.ai/mcp/{subdomain}`)
* Under **Advanced settings**, leave **OAuth Client ID** and **OAuth Client Secret** **blank**.
* Under **How your team connects**, choose **Individual sign-in** (each person signs in to Clarus with their own account).
Then click **Add**.
Every team member opens **Customize → Connectors** and selects **Clarus**, then clicks **Connect** and signs in with their own Clarus username and password.
Once connected, Clarus shows as available along with the tools Claude can use. You can set each tool to run automatically, ask for approval, or be blocked — Claude only ever sees the tools your organisation has given you access to.
Claude connects **as you** and uses your Clarus permissions, so it can change data as well as read it — for example updating an order or adjusting stock. Be specific about what you ask, and review any changes before confirming them.
## Troubleshooting
No — leave both blank. Clarus uses a sign-in (OAuth) flow that's set up automatically, so you don't create or paste any client ID or secret.
On a personal account, connectors live under **Customize → Connectors**. On a Team or Enterprise account, an owner adds connectors under **Organization settings → Connectors**, and members then manage their own sign-in under **Customize → Connectors**.
Double-check the address is exactly `https://agents.claruswms.ai/mcp/{subdomain}` with your real subdomain in place of `{subdomain}` and no trailing spaces. If you're an organisation owner, make sure you chose **Web** (not Desktop). Your subdomain is your organisation's short name in Clarus (see the [overview](/knowledgebase/integrations/ai-assistants-overview)).
Make sure you complete the Clarus sign-in **and** approve access in the pop-up window. If your browser blocks pop-ups, allow them for claude.ai and try again.
The assistant can only see and do what your Clarus account can. If you're missing data or an action fails, check your own Clarus permissions for that account, warehouse, or feature — or ask your administrator.
Yes — within your permissions it can make changes as well as read. Ask precisely and confirm anything important before it acts.