# Troubleshooting

Common problems when connecting or using the Quicklizard MCP connector, and how to fix them.

# I can't find the Quicklizard connector in my list

The connector has to be added to your Claude organization before anyone can connect to it, and on Team and Enterprise plans only an organization owner can add it.

  • Check you are looking in Customize → Connectors.
  • If it is not there, send your Claude administrator the Admin Setup guide.
  • If you are on Claude Pro or Max without an organization, you add it yourself — see the tip at the top of the Admin Setup guide.

# Sign-in fails, or says my user doesn't exist

Nearly always the wrong region. Quicklizard US and Quicklizard EU are separate environments with separate user directories — your login only exists in one of them.

  • Confirm which region you are on by checking the URL you use for the Quicklizard web app.
  • Disconnect the connector and connect the other one.
  • If both are named identically, ask your administrator to rename them clearly.

# Sign-in succeeds but then fails to connect

  • Make sure your Quicklizard account is active and your email address is verified. A user who has never completed sign-up, or whose invitation has expired, cannot authenticate.
  • Try Customize → Connectors → Disconnect, then Connect again. This clears a stale session, which is the most common cause.
  • If your company uses SSO for Quicklizard, tell your Quicklizard contact that you are connecting through the MCP connector — SSO through the connector may need to be enabled for your account.

# Claude says it doesn't have access to Quicklizard

The connector is connected but not switched on for the conversation. In the chat, click +, hover Connectors, and toggle Quicklizard on. It is a per-conversation switch — see Step 3 of User Setup.

# Claude keeps asking permission for every lookup

You approved a single call rather than the tool. Answering one question often takes several lookups, so this gets tedious fast.

When the prompt next appears, choose Always allow rather than Allow once. Your administrator can also set the connector to Always allow for everyone — see Step 5 of Admin Setup.

# A feature I was told about is missing

Claude caches the tool list from when you first connected, so new tools do not appear automatically.

Open the connector under Customize → Connectors, click the menu next to Disconnect, and choose Refresh tools list. See Keeping the tool list up to date.

# I can't see an account, product set or channel I expect

The connector uses your Quicklizard permissions. Claude can only reach the accounts, product sets and channels your own user can reach in the web app.

  • Confirm you can see the data in the Quicklizard web app while logged in as yourself. If you cannot see it there, this is a Quicklizard permissions matter, not a Claude one.
  • Ask whoever administers your Quicklizard users to extend your scope.
  • If your company has several Quicklizard accounts, tell Claude which one you mean — for example "in the DE account, show me…".

# Answers look wrong or out of date

  • Be explicit about dates. Say "1–31 August" rather than "last month" if precision matters.
  • Name the channel. Figures aggregated across channels can look surprising if you expected one.
  • Ask Claude to show its working. Try "which tool did you use and what filters did you apply?" — that usually reveals a mismatch between what you meant and what was fetched.
  • Start a fresh conversation. In a long chat, Claude may be reusing an earlier, narrower result. A new conversation re-fetches cleanly.

# Requests are slow or time out

Very broad questions across a large catalog can take a while, and may time out.

Narrow the request — a single channel, a shorter date range, or a specific group — and build up from there. If a narrow request also times out, contact support.

# Still stuck?

Contact your Quicklizard representative or our support team, and include:

  • which connector you used (Quicklizard US or Quicklizard EU);
  • your Quicklizard account and user email;
  • the prompt you tried;
  • the exact error text Claude showed you.