Article Contents
Introduction
Connect your Claude account and ask questions about your WISK data in plain language: what’s in stock, what to order, how last month’s variance looked, which items changed price. Claude reads your live WISK data through a secure connection that you control and can switch off at any time.
Setting it up takes about a minute.
Before you Start
You need:
A WISK login (the email and password you use at web.wisk.ai).
A paid Claude plan (Pro, Max, Team or Enterprise). Custom connectors are not available on Claude’s free plan.
WISK never sees your conversations with Claude, and Claude only sees the WISK data you would see yourself.
Step 1 — Add WISK as a connector in Claude
In Claude, open Settings → Connectors.
Click Add custom connector.
Paste this address:
https://mcp.wisk.ai/mcpName it WISK and click Continue
Claude checks the address and fills in the rest. Leave the detected settings as they are:
Authentication: Always required (marked Detected).
OAuth client: No client ID — register one automatically (marked Detected). Do not switch to Use Anthropic's hosted client metadata, even though Claude labels it Recommended — WISK does not support it and the sign-in will fail.
Managed authorization (shown on some team accounts): leave it off.
Additional request headers: leave empty
Click Add. WISK now appears in your connector list, but you are not connected yet — the list only stores the address. The sign-in happens from a chat.
Open a new chat, click the + button in the message box, choose Connectors (or Tools) → Add connector → Browse connectors, find WISK and click Connect to Claude. A WISK sign-in window opens.
Step 2 — Sign in to WISK and choose the level of access
Claude opens a WISK page in your browser.
Important: If you're already signed in to WISK in your browser, it will take you to Step 2 immediately. Make sure you're signed in with the correct user account that you want to connect.
Sign in with your WISK email and password.
Read the notice. WISK tells you it has not verified the app that is asking for access, and shows the web address your access will be sent to. For Claude that is a claude.ai address. If you did not start this yourself, or the address is not the app you are using, click Deny.
Check the level of access. Connections are read-only: Claude can look at your data and answer questions, but cannot change anything in WISK.
Click Approve. You are sent back to Claude and the connection is ready.
Step 3 — Ask WISK something in Claude
Try:
“What’s my current stock of Grey Goose?”
“What should I order from Southern Glazer’s this week?”
“What was my variance last month, and which five items were worst?”
“Which items went up in price on invoices in the last 30 days?”
“Show me the last three inventories for the main bar and how the total value changed.”
“Compare beverage sales to depletion for the Downtown venue in August.”
If you have more than one venue, just name it in your question. If you leave it out and it matters, Claude will ask.
What Claude can and cannot see
Claude gets exactly what your WISK account gets: the venues you are assigned to, and only what your WISK role allows. It cannot reach another venue, another user’s data, or anything your permissions hide from you.
One connection covers every venue you have access to. You do not need to connect once per venue.
Revoking access
You can cut Claude off at any moment, from either side:
In WISK:
In Claude: Settings → Connectors, remove WISK.
Troubleshooting
Claude says the WISK connection has expired or asks me to reconnect.
Connections refresh automatically. If Claude still asks, remove the WISK connector in Claude and add it again.
Claude says it can’t make a change because the connection is read-only.
That is expected: for security reasons connections are read-only for everyone.
Claude can’t find one of my venues.
Claude only sees venues your WISK account is assigned to. Ask your WISK administrator to add you to the venue.
I got a page saying “WISK has not verified this app” and I’m not sure.
That notice appears for every connection, including Claude, because anyone can build an app that asks for WISK access. The check that matters is the address shown under it: it should belong to the app you are connecting from. If in doubt, click Deny and contact support.




