Connect Claude to your studio with the Studiohaus MCP server.

MCP is the open standard AI assistants use to reach outside tools. Claude, ChatGPT, Cursor and Claude Code all speak it. Most practice-management software for interior designers has no MCP server at all, which means your assistant knows nothing about your projects unless you paste it in. Studiohaus is the exception: connect once, and the AI you already use can ask your studio questions directly.

What your assistant can do once connected

The server exposes three tools. That is the whole surface.

• List projects. Every project your role can see, with client name, status, phase and key dates.
• Project overview. One project in full: client contact, address, phase, dates, and open invoice totals when your role includes financials.
• Project activity.A chronological feed for a date range: communication-log entries, completed tasks, client approvals on design boards, and invoice events. Built for “what happened on the Lin project this week?”

Ask in plain words. “Draft a weekly update for each active project using my template.” “Which projects have an overdue invoice?” “What did the client approve on the Marchetti board since Monday?” The assistant calls the tools, reads the answers, and writes. Your email template lives in your AI, not in Studiohaus; the server supplies facts only.

What it will never do

There are no write tools. The server cannot create or edit a project, task, invoice, message, contract or board. Every query runs through the same row-level security as the app, as the person who connected it, so it sees your studio only, and within it only what your role allows. Financial figures return a “not permitted” error for roles without the financials permission rather than leaking numbers. Requests are rate-limited per connection. Revoke in Settings and the next request fails, no redeploy, no waiting.

Connecting Claude

1. In Claude, open Settings → Connectors → Add custom connector.
2. Enter the name Studiohaus and the URL https://platform.studiohaus.app/api/mcp.
3. Claude opens a Studiohaus sign-in. Sign in as an owner or studio admin and approve. That is a standard OAuth consent; no token to copy.
4. Start a chat, enable the Studiohaus connector, and ask for your projects.

Connecting Claude Code, Cursor, or another client

Tools that take a URL and a bearer key use a personal token instead. In Studiohaus go to Settings → Integrations → Connected AI, create a token with a label, and copy it once. Then add the server to your client. For Claude Code:

claude mcp add --transport http studiohaus https://platform.studiohaus.app/api/mcp \
  --header "Authorization: Bearer sh_pat_..."

For a JSON-configured client:

{
  "mcpServers": {
    "studiohaus": {
      "url": "https://platform.studiohaus.app/api/mcp",
      "headers": { "Authorization": "Bearer sh_pat_..." }
    }
  }
}

Tokens are shown once and stored hashed. Each token lists its last use in Settings and can be revoked there by an owner or studio admin. The step-by-step version with screenshots lives in the help center.

Why a design studio would want this

The weekly client update is the clearest case. Most studios write it from memory on Friday afternoon, re-reading each project to reconstruct the week. With the connector, the assistant pulls the last seven days of activity per project and drafts each update in the studio’s own voice, ready to edit and send. The same connection answers “what’s outstanding across all projects” or “which phase is every job in” without opening the app. See the note on weekly client updates for the workflow around it.

Questions