Propick Integration MCP

ae.propickPublished by propick.aeOfficial publisherv1.0.0Updated Oct 24, 2026

Manage your real-estate stock on Propick (Dubai): bulk listing sync, lookups and run reports.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Propick MCP server that lets an assistant manage Dubai real-estate stock: bulk listing sync, lookups and run reports.

What you can do
  • Sync property listings in bulk to a Propick account.
  • Look up existing listings and stock records.
  • Run reports on import and listing activity.
  • All actions go through a Propick import channel tied to an integration key.
When to use it
Useful when you manage Dubai real-estate inventory on Propick and want an assistant to push or reconcile listings in bulk and pull reports, instead of editing them by hand in the cabinet.
Requirements
A remote streamable HTTP endpoint at propick.ae; no local package. A Propick account and an integration key (ppk_live_...) created in the Propick cabinet when setting up an import channel, sent as an Authorization bearer header. OAuth is declared as required.
Before you install
The Authorization header carries a live integration key that grants access to your Propick stock; keep it out of logs and shared transcripts. Bulk sync and import operations can create or overwrite listing data, so review changes before running them. Listing data is sent to Propick's servers.

Installation

In SourceWeft

  1. Open Propick Integration MCP 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/ae.propick%2Fpropick/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": {
    "propick-integration": {
      "type": "http",
      "url": "https://propick.ae/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 16, 2026

Score

67% 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.

  • 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.