Propstack MCP

What ashev87/propstack-mcp MCP server does

The ashev87/propstack-mcp MCP server gives AI assistants access to Propstack CRM data and workflows used by real estate agencies. It covers contact records, property listings, sales and rental deals, development projects, search profiles, activities, calendar events, emails, and attached documents.

Contact tools support searching by names, email addresses, phone numbers, status, tags, broker, GDPR state, and custom fields. Phone lookups ignore formatting, which supports caller identification workflows. Contacts can be created, updated, soft-deleted, and associated with lead sources. Search and retrieval operations can limit returned fields to reduce the personal data sent to the connected language model.

Property tools handle listing search, detail retrieval, creation, and updates. Searches can filter by property type, marketing type, status, location, rooms, area, price, rent, construction year, projects, and custom fields. Deals link contacts to properties and can be created, searched, and moved through pipeline stages. Search profiles capture buyer or renter requirements such as cities, budget, room count, space, and feature preferences.

How it works

The server runs locally as an MCP process and sends requests to Propstack using the configured API key. An MCP client invokes individual tools with structured parameters. Lookup tools provide IDs needed by other operations, such as property statuses, contact sources, deal pipelines and stages, tags, custom fields, users, and reservation reasons.

Tasks provide a shared endpoint for notes, reminders, appointments, and cancellations. Events can be queried by date, broker, contact, property, or state. Email tools use Propstack templates and a broker account connected to Propstack. Documents are listed or uploaded as base64 data URIs and attached to exactly one contact, property, or project.

The server also includes composite workflows such as contact dossiers, property performance reports, pipeline summaries, lead intake, and matching contacts to properties. These operations combine CRM data into higher-level responses rather than requiring every underlying lookup to be called separately.

Setup and configuration

Install and run the ashev87/propstack-mcp MCP server with Node.js and the published package:

npx -y propstack-mcp-server

Set PROPSTACK_API_KEY before starting the process. The key is created in Propstack under the administration API-key settings, and its permissions determine which read and write operations are available. Claude Desktop and Cursor configurations can launch the server with the same command and pass the key through their environment settings. The project also documents use with ChatGPT connectors and Claude Code.

Limitations and notes

The server sends Propstack personal data to the connected language model. The Propstack customer remains responsible for the applicable data-controller obligations and should use the fields parameter where narrower contact, property, or deal responses are appropriate. Write operations may require specific Propstack permissions and valid IDs from the relevant lookup tools.

Email sending depends on a broker with a connected email account and a valid Propstack template ID. Uploaded documents must be supplied as base64 data URIs. Contact deletion is a soft delete that places the record in a 30-day recycle bin rather than immediately removing it permanently.