> For the complete documentation index, see [llms.txt](https://docs.reportpundit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportpundit.com/knowledge-base/settings/mcp-connector/report-pundit-and-claude-troubleshooting.md).

# Report Pundit and Claude: troubleshooting

Find your symptom below. Each entry stands on its own, so you can jump straight to the one that matches.

If none of these fit, [contact support](https://claude.ai/contact-support). Never include your MCP Access URL or token in a support message, since it grants access to your reports. Tell us the error you saw instead.

### Setup problems

#### I cannot find the MCP Access URL in Report Pundit

It is under **Settings**, then **Account Details**, in the row labelled **MCP Access URL** near the bottom of the panel. Click the copy icon next to it.

Do not use the **Shop Key** row directly above it. That is a different credential and will not work in Claude.

#### Claude will not accept my URL

The URL has to be pasted whole, including everything after `?token=`. Copy it again using the copy icon in Report Pundit rather than retyping or copying part of it by hand, and check there is no space at the end.

#### My Add custom connector dialog looks different from the screenshots

Claude has more than one version of this dialog. If yours shows the name, URL and Advanced settings on a single screen, fill in the name and URL, leave Advanced settings alone, and confirm. If yours has a **Continue** button, follow the steps in [How to connect Report Pundit to Claude](https://claude.ai/connect-report-pundit-to-claude).

#### It says "You're not connected to Report Pundit yet"

This is expected right after you add the connector. Adding it and connecting to it are two separate actions. Click **Connect** on that screen to finish.

#### I am on a Team or Enterprise plan and cannot add the connector

Only an organisation Owner can add a custom connector on these plans. Ask your Owner to add it, then find **Report Pundit** in your own **Connectors** list and click **Connect**.

#### I have added the connector but Claude says it has no Report Pundit tools

The connector is not switched on for that conversation. Click the **+** button in the message box, open **Connectors**, and switch **Report Pundit** on. If it is already on, start a new chat and try again.

#### Everything looks right but nothing works

Check your Report Pundit plan under **Settings**, then **Account Details**. The Claude connector requires **Essential Plus** or higher.

> **TO CONFIRM:** what a user below Essential Plus actually sees. Replace this note with the specific error or behaviour so people can identify it.

### Wrong data

#### Claude cannot find my report by name

Ask for the list first, then use the name as it appears:

> List my Report Pundit reports.

You can also give a keyword and let Claude find it:

> List my Report Pundit reports with "tax" in the name.

#### Claude ran a different report than I meant

This usually happens when several reports share a name. Rename them in **My Reports** so each is distinct, or tell Claude which one you want by its report type:

> Run the Sales one, not the Fulfilment one.

#### The report names Claude lists are not mine

The connector is pointing at a different store. In Claude, go to **Settings**, then **Connectors**, and open **Report Pundit**. The URL it is using is shown there with the token partly hidden. Compare the visible characters against the MCP Access URL of the store you meant to connect, and edit the URL if they differ.

#### The report ran but returned no rows

Almost always the date range or a filter. Ask:

> What date range and filters did that run use?

Then check the report's filters in **My Reports**. A report built for one purpose often excludes rows you would want for another.

#### The numbers do not match my Report Pundit export

Ask Claude to show its working:

> Which report, what date range, what filters, and how did you calculate that?

Three things account for nearly all differences. The **date range**, since Claude uses the report's saved range unless you ask for another. A **filter** on the report. Or your **Shop Time Zone**, which shifts orders near the start and end of a period. You will find your time zone under **Settings**, then **Account Details**.

If none of those explain it, the report may be large enough that results were cut short. See [Getting accurate results from large reports in Claude](https://claude.ai/claude-large-reports-best-practices).

#### The dates came out wrong

Give the range in words rather than numbers. `1 August 2026 to 31 August 2026` is unambiguous. `08/01/2026` is read differently in different countries.

#### I asked for inventory for last month and the answer looks odd

An inventory on hand report describes stock now, not stock over a period, so a date range does not apply to it. For stock over time, use an inventory snapshot report instead.

### Runs and performance

#### The report is taking a long time

Run time depends on the report and the period, not on Claude. Wide reports over long date ranges take as long as they would in the app.

To stop it:

> Cancel that report run.

Then run it again over a shorter range, which is usually much faster.

#### The run failed

Try once more before assuming something is broken, since single failures are often transient. If it keeps failing, run the same report in Report Pundit. If it fails there too, the problem is the report rather than the connector.

#### Claude keeps re-running the same report

Each new chat starts empty, so a report pulled in one conversation is not available in another. Stay in one conversation and ask follow-up questions there. Those are answered from data Claude already has and are instant.

### Access and security

#### I regenerated my token and Claude stopped working

Regenerating replaces the token, and the old URL stops working immediately. Copy the new MCP Access URL from **Settings**, then **Account Details**, then update the connector's URL in Claude under **Settings**, then **Connectors**.

#### I think my MCP Access URL has been shared

Regenerate it using the circular arrow icon on the **MCP Access URL** row, then update the URL in Claude. The old one stops working straight away.

To remove access entirely rather than replace it, use the delete icon on the same row.

#### How do I stop Claude reading my reports?

Any of these work, from least to most permanent:

* Switch the connector off for a conversation using the **+** menu.
* Remove the connector in Claude under **Settings**, then **Connectors**.
* Delete the MCP Access URL in Report Pundit, which revokes access regardless of what is configured in Claude.

### Related articles

* [How to connect Report Pundit to Claude](https://claude.ai/connect-report-pundit-to-claude)
* [How to pull a report into Claude](https://claude.ai/pull-saved-report-into-claude)
* [Getting accurate results from large reports in Claude](https://claude.ai/claude-large-reports-best-practices)
* [Report Pundit and Claude: FAQ](https://claude.ai/claude-connector-faq)
