Open House Copilot

com.openhousecopilotPublished by openhousecopilot.comOfficial publisherv1.0.0Updated Oct 24, 2026

AI open-house assistant for agents: sign-in kiosk + automated, consent-aware follow-ups.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote, OAuth-protected MCP endpoint for an AI open-house assistant that runs a sign-in kiosk and sends consent-aware follow-ups for real estate agents.

What you can do
The manifest lists no tools, so capabilities are known only from the short description. It presents an AI open-house assistant aimed at real estate agents. It covers a sign-in kiosk for open-house visitors. It also handles automated follow-ups that are described as consent-aware.
When to use it
Consider it if you are a real estate agent or team running open houses and want visitor sign-in plus automated follow-up handled through an assistant. The limited public description makes it hard to judge fit beyond that.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. OAuth sign-in is required. No environment variables, headers or packages are declared.
Before you install
It collects open-house visitor sign-in data and sends automated follow-ups, so consent handling and privacy of visitor contact details matter. The provider states follow-ups are consent-aware, but the manifest lists no tools, so verify what data is stored and sent before relying on it.

Installation

In SourceWeft

  1. Open Open House Copilot 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/com.openhousecopilot%2Fopenhouse-copilot/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": {
    "open-house-copilot": {
      "type": "http",
      "url": "https://mcp.openhousecopilot.com/mcp"
    }
  }
}

README

This repository has no README.

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 16, 2026

Score

60% 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
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.