Skip to main content

Troubleshooting

Common Koongo MCP problems and fixes: connecting and login, project/data readiness, plan add-ons, integration wizard issues, feed export, safety recovery, and how to report a bug to Koongo.

Something not working as expected? Find your symptom below. For connection and login problems specifically, the full step-by-step is on Installation & Connection.

Fastest fix: ask the assistant itself - "That failed. Explain the error in plain language and tell me how to fix it." It can read the exact error and walk you through it.

Connecting & signing in

Symptom

Fix

Can't connect / 403 "forbidden"

Your IP isn't on the allow-list (or it changed). Re-submit the beta form with your current public IP. No VPN needed.

401 "unauthorized"

Your static token is wrong/expired/revoked - generate a new one (My Account → Security → MCP API Access), or switch to OAuth.

Login opens but loops / won't re-authorize

For the mcp-remote bridge, clear the cached login: delete the ~/.mcp-auth folder and reconnect.

Client only offers "SSE"

Koongo serves Streamable HTTP at /mcp, not the old HTTP+SSE. Use the mcp-remote bridge for SSE-only clients.

Full connection troubleshooting (per client, per OS) lives on Installation & Connection.

Projects & data

Symptom

Fix

It asks "which project?"

Your account has more than one project. Name it: "Use project <name>." With a single project it's picked automatically.

"Store data isn't ready" / import not finished

Your catalogue is still importing. Ask "Is my store data ready?" and wait until it reports OK before mapping or creating feeds.

A product change isn't showing up

Data refreshes on import (and after you apply an enrichment). Ask the assistant to "check the import status" and retry once it's done.

Plan & add-ons

Symptom

Fix

"Add-on required" when enriching products

Adding sources needs the Additional Sources add-on. The assistant gives you an upgrade link - enable it on your plan, then retry. See Enrich Products with New Attributes.

"Quota / limit reached" when creating a feed or channel

You've hit your plan's channel limit. Remove an unused feed/integration, or upgrade your plan.

Integrations & the wizard

Symptom

Fix

The wizard is "stuck" at the connection step

That step is finished by you, in the browser - the assistant can't enter channel credentials. Open the link it gave you (OAuth or settings), complete it, then say "continue".

"Step can't be skipped" / wrong order

Wizard steps run strictly in order. Let the assistant do them one at a time rather than jumping ahead.

Required attributes won't go to zero

Some required fields appear only after category mapping. Do Category Mapping first, then ask the assistant to refresh the attributes.

Category mapping "needs confirmation"

The category rules are shared with other feeds on the same taxonomy. Review the list of affected feeds the assistant shows you, then approve.

Feeds & export

Symptom

Fix

Feed status shows error

Ask the assistant to read the error message. It's often an unmapped required attribute - fix it and re-export.

"Not submittable"

This is a file feed the channel pulls itself. You don't submit it - share the feed URL with the channel instead.

My change isn't in the file

Settings, filters and mapping are saved first and only appear after export. Ask the assistant to export, then check.

"Still generating"

Export runs in the background. Ask the assistant to check the status; it will wait until the file is generated.

Safety

"I accidentally published everything to the live channel." Finishing the wizard in AUTO product mode publishes every matching product. Ask the assistant to "pause this integration" or "switch it to MANUAL mode" right away. Next time, set MANUAL first, publish one product as a dry run, and only then release the rest.

Report a problem to the developers

Koongo MCP is in closed beta, and your feedback shapes it. If something doesn't feel right - a tool errored and you couldn't get past it, a result was wrong or confusing, a capability you needed is missing, or you and the assistant had to work around a limitation - you can send it straight to the Koongo developers through the assistant.

Just say:

Report this to the Koongo developers as a bug.

The assistant asks for your OK, then files one report describing what you were trying to do, what happened, and the exact steps it took - so an engineer can reproduce it. You get back a report ID.

These reports are product feedback for the Koongo team - they don't change your task and you don't have to wait for them. The assistant never includes passwords, tokens or personal data (they are stripped out defensively). You can report an outright error, a wrong or confusing result, a missing capability, or just a suggestion.

Still stuck?

  • Ask the assistant to explain the last error and suggest the next step.

  • Have the assistant report the problem (above), or contact Koongo support and mention you're on the MCP closed beta, with the exact message you saw.

Did this answer your question?