Troubleshooting
TL;DR
Xnurta MCP errors trace to a few causes you can fix yourself: a wrong token, an expired authorization, a skipped skills step, old permissions after new access is switched on, or a date range that is not what you assumed. This guide is for marketers and agency teams who connect Claude, ChatGPT or another MCP client to Xnurta MCP and want to match an error to its fix in one pass. It covers 12 errors in three tables, and none of the fixes needs write access.
get_user_authorized_context. It returns your user ID and authorized ad accounts when the connection works.You ask the assistant to call get_user_authorized_context. If it returns your user ID and your authorized ad accounts, the connection works and the problem sits further down this page. Run it first. One message separates a connection problem from a skills problem or a data problem.
Xnurta MCP connects Claude, ChatGPT and other MCP clients to your Xnurta data through one address, https://mcp.xnurta.com/mcp. A failure at this step points to the sign-in, the token or the network.
Prompt: check the connection
Call get_user_authorized_context and list the ad accounts I'm authorized to access.
Everything in this guide is a read or a reconnect. Nothing here changes a campaign.
Five errors can stop a first connection, and each has a fix in the last column. Find what you see in the second column.
| # | What you see | What it means | The fix |
|---|---|---|---|
| 1 | A 401 error, connected with a token | The token is wrong or lacks the scope it needs. | In Xnurta, open MCP & Skill, click New token, choose the scope you need and give the new token to your assistant. Run the check again. |
| 2 | A 401 error, connected with OAuth | The authorization expired or lacks a newer scope. | Disconnect Xnurta MCP in your client, connect again, sign in and approve. |
| 3 | The request times out | The request did not complete. | Check your network connection, then run the check again. |
| 4 | "Add custom connector" is missing on Claude Team or Enterprise | Expected. On Team, only an Owner or Primary Owner can add a connector to the organization. On Enterprise, a custom role with library management access can also add one. | Ask your Claude admin (an Owner, Primary Owner or, on Enterprise, a custom role with that access) to add it once: Organization settings, Connectors, Add, Custom, Web, the address above, Add, with Advanced settings empty. Then connect yourself: Customize, Connectors, find the Xnurta connector, Connect. |
| 5 | A token will not work in Claude desktop, Cowork or claude.ai | These clients have no field for a token. | Use the custom connector and browser sign-in instead. On Free, Pro or Max: Customize, Connectors, +, Add custom connector, enter the address, Add. |
A token is shown once. You cannot view it again after you leave the page, so a lost token means a new token. With OAuth there is no token to manage, because you sign in with your own Xnurta login. The full setup lives in Connect Claude or ChatGPT to Xnurta MCP.
Four things go wrong here, and each traces to a missed step or an old connection that does not carry the new access.
| # | What you see | What it means | The fix |
|---|---|---|---|
| 6 | Connected, but the skills are missing | Adding a connector never installs skills. | In a new chat, ask the assistant to install them from the repository (prompt below). If it skips them, send the link again. |
| 7 | Write tools do not appear after your CSM turns on write access | Your existing connection still carries the old permissions. Signing in again on it keeps them. | Remove the connector and add it again, or create a new token with the scope you need. Then update your skills in a new chat. In Claude Code or Codex, tell the agent to replace the old configuration rather than add a second one. |
| 8 | The assistant can edit ads but cannot create campaigns | Writing comes in three kinds, each with its own permission scope. A scope that edits ads does not necessarily create campaigns. | Create a new token that includes the scope you need. On a connector, remove it and add it again once your CSM has switched the extra access on. |
| 9 | You asked for a change and nothing happened | For money, bids and archiving, the assistant shows a preview first and submits only after you confirm. | Read the preview, which lists the objects and each change from old value to new value, then confirm it. Campaign creation is all or nothing: if one campaign in the request fails validation, none are created. |
Skills are the routine your assistant follows for Xnurta tasks, such as what to pull for a Weekly Ads Report or how to run a Product Diagnosis. The connector gives access. The skills give the routine. One prompt in a new chat installs missing skills and updates the ones you already have, which is also the last step after any reconnect. More on what each skill does is in How an SOP becomes something an AI assistant can run.
Prompt: install or update the Xnurta skills
Please read the following GitHub repository, update my existing Xnurta Skills to their latest versions, and install any Xnurta Skills that are currently missing: https://github.com/Xnurta/Xnurta-MCP
Rows 7 and 8 both depend on write access being on for your account. If it is off, the assistant can still read everything you are allowed to see. It just cannot change anything.
The access rule
Generally available from 27 Oct for Sponsored Ads. Write access is turned on per account by your CSM.
Archiving cannot be undone, and campaigns cannot be deleted. If you only want a campaign to stop, pause it. Read-only vs read-write MCP for Amazon advertisers explains which access to start with.
Because it reads only what your own Xnurta login can see, and only as fresh as the platform. Three errors live here, and none of them is a connection fault.
| # | What you see | What it means | The fix |
|---|---|---|---|
| 10 | The wrong ad account, or one is missing | You see only the ad accounts your own Xnurta login carries, main accounts and sub-accounts included. | Run the check to list your authorized accounts, and name the account in every question. If one is missing, check which Xnurta login you signed in with, then disconnect and connect again with the right one. |
| 11 | The operation log comes back empty | Possible causes are the ad account, the window or the filters. | Confirm the ad account, keep the window inside about 15 months, and ask which filters the assistant used. A human-only filter returns nothing when an automation rule made the change, so widen it. |
| 12 | Numbers differ from the dashboard | Data follows the Xnurta platform's update cadence, not real time, and defaults to daily. | Compare the same account, the same dates and the same granularity. Hourly data exists for Sponsored Products, Sponsored Brands and Sponsored Display campaigns and for Sponsored Products keywords, with a window of about one week. Ask the assistant to state the account, dates and granularity it used. |
One more check for row 10. When you connect, you review the permissions and the ad accounts on the authorization page. If an account you expected is not on it, stop there and sign in with the login that carries it.
You ask the assistant for the operation log. It records human and AI actions on campaigns, ad groups, targets, bids, budgets and managed groups, and you can filter by operator to separate the AI, a person and an automation rule. Asking is a read, so it is safe to do mid-fix.
If a number moved and you suspect a change rather than a data delay, this is one way to tell. Who changed my Amazon campaign? walks through the questions to ask, with prompts.
FAQ
With a token, the token is wrong or lacks the scope it needs, so create a new one in MCP & Skill. With OAuth, the authorization expired or lacks a newer scope, so disconnect and connect again.
Adding a connector never installs skills. In a new chat, ask your assistant to read the Xnurta GitHub repository and install them, and send the link again if it skips them.
On Claude Team, only an Owner or Primary Owner can add a connector to the organization, and on Enterprise a custom role with library management access can also add one. Ask your Claude admin to add it, then connect with your own Xnurta login.
Yes. Remove the connector and add it again, or create a new token, because signing in again on the old connection keeps the old permissions. Then update your skills.
Check the ad account, keep the window inside about 15 months, and look at the filters. A filter for human actions returns nothing when an automation rule made the change.
Keep going
Xnurta MCP
Xnurta MCP is for Xnurta customers only. Create your MCP connection directly in the Xnurta platform. New to Xnurta? Book a demo and we'll walk through your account with you.
