Kvadrum

estate.kvadrumPublished by kvadrum.estateOfficial publisherv1.0.0Updated Oct 24, 2026

Real estate agency CRM: listings, clients, leads and viewings from your AI assistant (OAuth).

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Kvadrum is a remote real estate agency CRM that lets an AI assistant work with listings, clients, leads and viewings through an OAuth-protected connection.

What you can do
Work with property listings, clients, leads and viewings in a real estate agency CRM, as described in the registry entry. The manifest lists no individual tools, so the exact operations available are not documented here. Access is through a remote endpoint with OAuth sign-in.
When to use it
Useful for a real estate agency that already runs its CRM on Kvadrum and wants an assistant to reach its listings, clients, leads and viewings without switching apps.
Requirements
A remote MCP endpoint at kvadrum.estate reached over streamable HTTP, plus an OAuth sign-in to a Kvadrum account. No packages, environment variables or headers are declared.
Before you install
The connection is OAuth-protected and touches client, lead and viewing records, which are personal data; grant only the access you intend. The manifest lists no tools, so confirm what the assistant can read or change before connecting.

Installation

In SourceWeft

  1. Open Kvadrum 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/estate.kvadrum%2Fkvadrum/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": {
    "kvadrum": {
      "type": "http",
      "url": "https://kvadrum.estate/api/v1/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.0LatestOct 15, 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.