A 360-degree contact view is four calls collapsed into one, lead intake dedups and creates and logs and reminds in a single step, and the matcher ranks existing search profiles against a new listing rather than making you read them. Because it moves personal data out of the CRM and into whichever model you connect, use the fields parameter on the bulk reads and ask for only what the job requires.
An MCP server over the Propstack V1 API, covering the CRM's own entities plus a set of composite tools that bundle several calls into the workflows a broker actually runs.
- Contacts: search and filter, read one in full, create, update, soft-delete into a 30-day recycle bin, and look one up by phone number — the caller-identification path for a voice agent
- Properties (Objekte): search by address, ID or exposé, read one in full, create and update listings, and read the available statuses
- Deals linking an interested contact to a property, with pipelines and their ordered stages so a deal can be moved along
- Search profiles (Suchprofile) capturing what a buyer or renter wants — created, widened, narrowed and deleted — and a matcher that ranks contacts whose profiles fit a new listing
- Tasks as the single write path for activity: notes, to-dos, appointments and cancellations, created, updated and read back with their linked entities expanded
- The calendar and the activity feed: viewings, client meetings and notary appointments, alongside the read-only timeline of what has already happened
- Email through a connected broker account using a Propstack template, plus marking an email read, archived or categorised
- Documents on a property, project or contact — listed, and uploaded as a base64 data URI
- Relationships: record a contact as a property's owner (Eigentümer), or as a partner such as a buyer or tenant
- Development projects that group many units, with their images, floorplans and documents
- The lookup tables you need before writing anything: contact sources and statuses, property statuses, tags, custom field definitions, pipelines, activity types, cancellation reasons, geographic areas, users and teams
- Composite workflows: a 360-degree contact briefing assembled from four parallel calls, a property performance report with days on market and inquiry counts, a pipeline summary flagging stale deals, and a lead-intake flow that dedups, creates, logs and sets a reminder in one step
- Webhooks listed, created against chosen events, and deleted
A Propstack account and a V1 API key from Verwaltung > API-Schlüssel in crm.propstack.de, supplied as PROPSTACK_API_KEY — which endpoints are reachable follows from that key. Run it over stdio with npx -y propstack-mcp-server. Worth setting up front rather than later: the tools that return personal data in bulk — contact search, property search, deal search and the 360-degree view — accept an optional fields parameter, and naming only the fields a task needs keeps the rest of the CRM out of the model's context.
One command plus a key — npm install propstack-mcp-server, then supply credentials