Guides

Deploy an app straight from Claude with MCP

Q: What is the Inhaus MCP server URL?

https://mcp.inhaus.dev/mcp. It is the same for every AI tool and every workspace. The bare domain, without /mcp, does not work.

Q: Can a Claude Team or Enterprise owner add it for everyone?

Yes. An owner adds the connector once under Admin settings → Connectors. Each member then connects and signs in with their own Inhaus account.

Deploy an app from Claude with MCP: add the Inhaus MCP server as a custom connector, then ask Claude to put the app live behind your company login.

Updated 16 Oct 2026

To deploy an app straight from Claude, add Inhaus as a custom connector (an MCP server) at https://mcp.inhaus.dev/mcp, then ask Claude to "put this live". Claude calls the Inhaus deploy_app tool with the app's files and replies with a private link behind your company login.

This works in Claude on the web, the Claude desktop app and Claude Code. You never leave the chat, and you never copy an API key.

What MCP does here

MCP (Model Context Protocol) is the standard AI tools use to connect to other services. An MCP server gives the AI tools it can call. Inhaus runs a remote MCP server with thirteen tools, such as deploy_app, share_app, rollback and get_access_log. Once it's connected, you describe what you want in plain words and Claude picks the tool.

Every call acts as you, in the one workspace you approved, with your permissions. Claude can't do anything you couldn't do in the Inhaus dashboard.

Steps

Add the connector
Claude (web and desktop): go to Settings → Connectors → Add custom connector. Name it Inhaus and paste the URL below as the remote MCP server URL. Choose Add, then Connect.
Claude Code: run this in your terminal, then run /mcp and choose inhaus → Authenticate.
```
claude mcp add --transport http --scope user inhaus https://mcp.inhaus.dev/mcp
```
The URL is the same everywhere: https://mcp.inhaus.dev/mcp. Include /mcp at the end.
Approve on inhaus.dev
Your browser opens the Inhaus consent page. Check Signed in as shows the right email, pick the workspace and choose Allow. If the page asks you to sign in, open it in the browser where you're already signed in to Inhaus, or copy the link across.
Turn it on in the chat
In Claude on the web or desktop, open the + menu → Connectors and turn Inhaus on.
Build or open your app
Ask Claude to build something, or open the chat or folder where the app already is.
Ask Claude to deploy
```
Put this live on Inhaus as "Expense Claims".
```
Claude sends every file of the app to deploy_app. Inhaus builds it, scans it, and puts it live, usually in under a minute. Claude replies with:
- the app link, such as https://expense-claims--acme.inhaus.dev
- the app's page in Inhaus, for access, versions and activity
- the security scan result, and a fix for any issue it found
Share it
```
Share Expense Claims with the finance team, view only.
```
Claude calls share_app. Each person gets an email and signs in with their company account.

The tools Claude calls

You say	Claude calls
"Put this live", "deploy a new version"	`deploy_app`
"Share it with the sales team, view only"	`share_app`
"Which teams can I share with?"	`list_teams`
"It shows an error"	`get_logs`, then fixes and redeploys
"Store this API key safely"	`set_secret`
"Go back to the old version"	`rollback`
"Who opened it?"	`get_access_log`
"Let the whole company use it"	`submit_to_directory`

Inhaus tells Claude to check with you before anything hard to undo, such as deleting an app, listing it for the whole company or writing to its database.

FAQ

What is the Inhaus MCP server URL?

https://mcp.inhaus.dev/mcp. It is the same for every AI tool and every workspace. The bare domain, without /mcp, does not work.

Do I need an API key?

No. Claude signs in through your browser with OAuth. Inhaus has no API key option, because every call must act as a signed-in person.

Can a Claude Team or Enterprise owner add it for everyone?

Yes. An owner adds the connector once under Admin settings → Connectors. Each member then connects and signs in with their own Inhaus account.

Which workspace does Claude deploy to?

The one you picked on the consent page. To use another, disconnect and connect again. See Manage connections.

What if the deploy fails?

The previous version stays live. Claude gets the error and the last build log lines, fixes the problem and deploys again.

Is it safe to let Claude deploy?

Claude acts as you with your role, every action is in the access log, and every deploy is scanned. You can disconnect Claude at any time under Connect AI tool in the dashboard.

Next steps

Quickstart
Connect Claude and Connect Claude Code: every click.
MCP server reference