Help›Troubleshooting the MCP
Troubleshooting the MCP
Sign-in fails, your assistant doesn't see Kintsu or isn't allowed to do something? Here is the cause and the fix for each problem.
Below, you'll find the cause of each problem and what to do. Always start by asking your assistant: “Who am I in Kintsu?” You'll then see which account, organizations and role it's working with.
Before you start
Who: any role.
Plan: any plan.
You need: an assistant connected to https://mcp.kintsu.be, as described in Edit your site with your AI assistant.
Signing in fails
The Kintsu window doesn't open. Your browser is blocking a pop-up. Allow pop-ups, or first sign in at app.kintsu.be in the same browser. Then try again.
You see “This request is not valid or has expired.” You waited too long, or you opened an old link. Start again from your assistant.
You see “Your answer did not get through.” Click Allow again.
Your assistant reports “invalid_client” or “Client not found”. It remembers an old registration that Kintsu no longer knows. Clear it and connect again (see below).
You have to turn on two-step verification. Your role requires it, for example as a designer. Turn it on under Account › Security on app.kintsu.be and connect again.
Your assistant asks you to sign in again. This happens if you revoked its access, or if you haven't used it for a long time. Sign in and click Allow.
Clearing an old registration
VS Code. Open the Command Palette with Ctrl+Shift+P (⇧⌘P on a Mac) and choose Authentication: Remove Dynamic Authentication Providers. Remove Kintsu. Then restart the server: VS Code asks you to sign in again.
Claude Code. Type this command in Claude Code, choose kintsu, then Clear authentication:
/mcp
If that doesn't help, remove Kintsu and add it again, as in Connect Kintsu to Claude Code.
Claude, ChatGPT and Cursor. Remove Kintsu from your connectors, plugins or MCP servers and add it again. The steps are in the article about your assistant.
Your assistant doesn't see Kintsu
Kintsu isn't turned on in your chat. In Claude, turn it on through + › Connectors. In ChatGPT, type @ and choose Kintsu. In VS Code, choose the tools through Chat: Open Customizations › Tools or Configure Tools.
You haven't signed in yet. You added Kintsu but haven't clicked Allow yet. Sign in as described in the article about your assistant.
The address is wrong. Use https://mcp.kintsu.be, not app.kintsu.be. The address with /mcp at the end works too.
Your assistant doesn't think of Kintsu. Mention it in your request: “Look in Kintsu …”.
A company network blocks it. Ask your IT team to allow mcp.kintsu.be and app.kintsu.be.
Claude Free: you can have at most one custom connector.
ChatGPT: all tools of a custom MCP server are only available with Business, Enterprise or Edu, on the web. With Pro, you can only read.
Your assistant isn't allowed to do something
Your assistant works with your role's permissions, never more. If it says something isn't allowed (Kintsu then answers: “You are not allowed to do this.”), check the following:
Your role. Ask “Who am I in Kintsu?”. A Member can only read. An Editor can change the content, but not the design, the theme or the domains.
Design. Building sections and changing styles or the structure of your site is up to the designer, or the owner with Kintsu Studio. Your assistant will then suggest asking your designer.
The organization. Are you a member of several organizations? Name the right one: “Work in Bakkerij Peeters.”
Your subscription. If a payment is overdue or your subscription has ended, your assistant can look but not change anything. The owner can sort this out under Subscription.
Something that doesn't exist. “This item does not exist, or no longer exists.” means the name of a site, page or item is wrong. Have your assistant list your sites and pages first.
A confirmation that expires
Before your assistant publishes or does something big, it shows what will happen and asks for your approval. That confirmation is valid for 10 minutes, and only for exactly that change.
Did you answer too late? Kintsu tells the assistant the confirmation has expired. It asks again and shows you again what will happen. Then say yes again.
Did you change the request in the meantime? Then the confirmation no longer matches the change, and the assistant asks for a new one. That way, you always approve what actually happens.
Too many requests
Kintsu allows 120 requests per minute per user. If your assistant reports “Too many requests”, wait a moment. Split a big job into parts: first the pages, then the news.
Still stuck?
Email contact@kintsu.be. Include your assistant, what you asked, the error message and the time.
Checked on 4 November 2026.
Stuck?
Email us at contact@kintsu.be with the name of your site and what you tried. You'll get an answer within two working days.