Studiohaus

app.studiohausPublished by studiohaus.appOfficial publisherv1.0.0Updated Oct 24, 2026

Read-only MCP server for interior design studios: projects, overviews, weekly activity. No writes.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Read-only remote MCP server that lets an assistant look up interior design studio projects, overviews and weekly activity.

What you can do
  • Read project information for an interior design studio
  • Retrieve studio overviews
  • Review weekly activity summaries
  • All access is read-only; no tools are listed in the manifest, so exact capabilities are limited to what the provider documents.
When to use it
Useful when an assistant needs to answer questions about an interior design studio's projects, current overview or recent weekly activity without opening the studio platform directly.
Requirements
A remote endpoint at platform.studiohaus.app over streamable HTTP, with OAuth authentication required. No environment variables, headers or packages are declared.
Before you install
Access is granted through OAuth to studio data, so review the scopes requested during sign-in. The provider states the server is read-only and performs no writes, but the manifest lists no tools, so verify actual behavior before relying on it.

Installation

In SourceWeft

  1. Open Studiohaus in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.studiohaus%2Fstudiohaus/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "studiohaus": {
      "type": "http",
      "url": "https://platform.studiohaus.app/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.