Troubleshooting

• Check the URL is exactly https://mcp.inhaus.dev/mcp.
• Finish the sign-in: in Claude Code run /mcp, in Cursor open Settings → MCP and choose Login.
• In Claude and ChatGPT, turn the Inhaus connector on in the chat's tools menu.
• Start a new chat after adding the connector.

The connection was revoked or expired. Remove and add the connector again, or sign in again from your tool's MCP settings.

Each connection reaches one workspace. Disconnect the tool and connect again, picking the right workspace. See Manage connections.

Inhaus did not find an index.html or a server file. Check Project structure, or pass entry to deploy_app.

The code or a package uses Node.js built-ins, which the runtime does not have. Ask your AI tool to use web APIs (fetch, crypto.subtle, Response) or a package made for the browser or edge runtimes.

Large builds can take longer than the tool waits. The deploy keeps going and goes live on its own. Ask your AI tool to run list_apps in a minute.

There is already an app with that address in your workspace. To update it, ask your AI tool to deploy with that app's app_id. To make a new app, give it another name.

The workspace's 7 free days are over. Apps keep running, but deploying needs a plan. An admin (or the owner of a personal workspace) chooses one from the link in the error, or from Plan & billing. See Plans.

The previous version stays live. Fix the SQL in a new migration file, or fix the failing file if it never ran, and deploy again.

In a company workspace, the domain must be on the allowed list. Check the app's Security tab for an open domain request, and add a reason for your admin. Blocked requests also show in the access log as Blocked.

• Secrets are only available in server code, not in the browser.
• Check the exact name in the app's Secrets tab. Names are case-sensitive.

Ask your AI tool: "Check the logs for this app and fix the errors." It uses get_logs. Also check the browser console for errors in browser code.

It was probably asleep after 14 days without visits. The first request wakes it up; the next ones are fast.

The latest version has blocking security issues. The Share dialog says how many. Fix them and deploy again. See General access.

In a company workspace, this submits the app to the company directory. If your admin approves submissions, it opens to everyone once an admin approves it. Check the app's directory status on its page.

Ask it to list them: "Which teams are in our Inhaus workspace?" It uses list_teams. If none come back, an admin can create groups under Admin → Members → Groups.

They signed in with an account outside your company, such as a personal Gmail. Ask them to switch to their company account. To let outside people in, your admin must allow guests.

Nothing was shared. Give the email address instead of the name.

You are its only admin. Make someone else an admin under Admin → Members first, or delete the workspace if you are the only person in it. See Leave or delete.