Troubleshooting
Fixes for sign-in problems, missing tools, the wrong organization and requests Lahuta refuses.
Most problems come down to three things: the sign-in, whether Lahuta is switched on in the chat you're using, and what your role allows. Start with the section that matches what you see.
Connecting and signing in
The sign-in page never opens
Check the address first. It must be exactly https://api.lahuta.org/mcp, with nothing after /mcp.
Some clients wait for you to start the sign-in:
| Client | How to start it |
|---|---|
| Claude | Open Customize → Connectors and select Connect next to Lahuta. |
| Claude Code | Run /mcp, select lahuta and follow the prompt, or run claude mcp login lahuta. |
| Codex | Run codex mcp login lahuta. Adding the server doesn't sign you in. |
| Cursor | Open Customize in the sidebar and use the log-in button next to Lahuta. |
If your client has no way to sign in through the browser, it can't connect to Lahuta. See Other clients for what a client needs.
The client asks for an API key or a token
Leave it empty. Lahuta doesn't use API keys for AI assistants. You sign in with your Lahuta account instead. Keys from the Org API won't work here. If the client won't continue without a key, it doesn't support MCP sign-in and can't connect.
The client asks for an SSE URL, or you see "405"
Lahuta supports only the current transport, streamable HTTP. Pick the HTTP or streamable HTTP option in your client and use https://api.lahuta.org/mcp. Clients that only support the older SSE transport can't connect.
You see "403" when connecting
Lahuta refuses connections made from code running inside a web page. Use a desktop app, a command-line tool or a hosted assistant like Claude, ChatGPT or Gemini.
It keeps asking you to sign in, or says "401" or "needs authentication"
Your sign-in expired or was cleared. Sign in again:
- In Claude Code, open
/mcp, select lahuta, choose Clear authentication and authenticate again. - In other clients, disconnect Lahuta and connect it again.
"Session not found" or "404" in the middle of a chat
Your client's connection to Lahuta was reset on our side, for example after an update. Most clients reconnect on their own and you won't notice. If yours shows this error, start a new chat or restart the client. If it keeps happening, disconnect Lahuta and connect it again.
Tools and chats
Lahuta's tools don't show up
Connecting isn't always enough. Most assistants also need Lahuta turned on where you chat:
| Client | Where to turn it on |
|---|---|
| Claude | Select + in the message box, hover over Connectors and switch Lahuta on. |
| ChatGPT | Open the + menu, choose Developer mode and select Lahuta. |
| Gemini | Type @ and pick Lahuta. |
| Cursor | Use an Agent chat, and check Lahuta is switched on under Customize. |
| Claude Code | Run /mcp and check Lahuta shows as connected. |
The assistant is working in the wrong organization
Ask it "which Lahuta organization are you using?" If it's the wrong one, name the right one in your request, like "in northside-pottery, ...". The slug is the last part of your dashboard address. To change the default for good, disconnect Lahuta, connect again and choose the other organization when you sign in. See Organizations and permissions.
This is also the first thing to check when the assistant says it made a change that you can't find in the dashboard.
The assistant says it can't add photos
The assistant can't upload new files. Upload photos in the dashboard first. Then the assistant can find them in your file library and attach them, for example to a product's gallery.
Refused requests
When Lahuta refuses a request, nothing changes, and the assistant gets a reason and a message. Here's what the common ones mean.
"Forbidden" with a permission
Your role in that organization doesn't allow the tool. The message names the permission, like events:manage. Ask an admin to do it, or to change your role. See what each role can do.
"NotFound" for an organization
The organization slug or id is wrong, or you're not a member of that organization. Lahuta answers both the same way. Check the slug in your dashboard address, or ask the assistant to list your organizations.
If every request fails this way, even when you don't name an organization, disconnect Lahuta, connect again, and choose your organization when you sign in.
Refused with a reason about your setup
Some actions need something set up in the dashboard first, and Lahuta says what's missing. The usual ones:
| What you asked for | What it needs |
|---|---|
| Paid tickets, or putting products or services on sale | A Stripe account that can take payments. See Get paid. |
| Putting a shipped product on sale | Shipping or pickup set up, and a weight on everything you ship. See Shipping and pickup. |
| Putting a download on sale | A file attached to it. |
| Sending a campaign | At least one person in the audience it can reach. If it sends from one of your connected mailboxes, that mailbox has to be working, and a text part needs an enabled number. See Email and Text messaging. |
Other refusals protect things that already happened. A campaign can only be edited while it's a draft, and campaigns and newsletter editions can't be cancelled once they've started going out. Only draft offers can be sent. A live blog post can't be deleted, so unpublish it first. An event's last remaining date can't be cancelled.
"Invalid params"
The assistant sent the details in the wrong shape, like a date in the wrong format. It usually notices and tries again. If it doesn't, rephrase your request with the exact names, dates and amounts.
"Tool execution failed due to an internal server error."
Something went wrong on Lahuta's side. Try again in a minute. If it keeps happening, contact us with the time and what you asked for.
Still stuck?
Use the Support button at the bottom of the dashboard sidebar, or email support@lahuta.org. Tell us which assistant you use, what you asked, and the exact error it showed.