MCP SERVERRuns a Propstack real-estate CRM from a conversation — contacts, properties, deals, search profiles, viewings and the briefing you want before a call.
LABSCO SUMMARY
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.
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
USE CASES
Identify the caller by phone number, then pull the full briefing on them.
Run the intake flow: it checks for duplicates, creates or updates the contact, logs the notes and sets the follow-up.
Create the property, then rank the contacts whose search profiles match it.
Turn the description into a search profile, and adjust the budget or area as it changes.
Read the per-stage summary with stale deals flagged, then open the deals that need attention.
Check what is already in the calendar, then create the appointment with its linked contact and property.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_contactCreate a new contact in Propstack CRM.
Use this tool to:
Auto-upserts: if a contact with the same email or old_crm_id already exists, it will be updated instead of creating a duplicate.
Use get_contact_sources first to find valid source IDs.
create_dealCreate a deal linking an interested contact to a property in Propstack.
A deal represents a contact's interest in a property and tracks it through pipeline stages (e.g. Anfrage → Besichtigung → Reserviert → Notartermin → Verkauft).
Use this tool after:
Requires client_id, property_id, and deal_stage_id. Use list_pipelines or get_pipeline to find valid pipeline and stage IDs.
create_ownershipLink a contact as the OWNER (Eigentümer) of a property.
Use this tool to:
The ownership appears on both the contact's and the property's record.
create_partnershipLink a contact as a PARTNER (buyer, tenant, etc.) to a property.
Use this tool to:
The name field describes the role (e.g. "Käufer", "Mieter", "Verwalter").
create_propertyCreate a new property (Objekt) in Propstack CRM.
Use this tool to:
Use get_property_statuses to look up valid status IDs. Use the relationships_attributes array to link an owner contact on creation.
rs_type values: APARTMENT, HOUSE, TRADE_SITE, GARAGE, SHORT_TERM_ACCOMODATION, OFFICE, GASTRONOMY, INDUSTRY, STORE, SPECIAL_PURPOSE, INVESTMENT.
rs_category provides sub-types (e.g. PENTHOUSE, VILLA, MAISONETTE for APARTMENT/HOUSE).
create_search_profileCreate a search profile (Suchprofil) for a contact in Propstack.
This is THE killer feature for an AI real estate assistant. When a buyer or renter describes what they're looking for in natural language, map it to structured search criteria:
Example conversation: "Herr Weber sucht eine 3-Zimmer-Wohnung in Berlin oder Potsdam, Budget 300.000–400.000 €, muss einen Balkon haben" → client_id: <Herr Weber's ID> marketing_type: "BUY" rs_types: ["APARTMENT"] cities: ["Berlin", "Potsdam"] number_of_rooms: 3, number_of_rooms_to: 3 price: 300000, price_to: 400000 balcony: "true"
Mapping guide:
Feature booleans use strings: "true" = required, "false" = excluded, omit = don't care.
Use radius search (lat/lng/radius) for "within 5km of Alexanderplatz".
create_tagCreate a new tag/label (Merkmal) in Propstack.
Tags are used to categorize contacts, properties, and activities. Optionally assign to a parent super-group (Obermerkmal) for hierarchy.
Examples: "Penthouse-Käufer", "VIP", "Kapitalanleger", "Erstbezug".
create_taskCreate a task (note, to-do, appointment, or cancellation) in Propstack.
This is the central write endpoint for ALL activity types. The mode is determined by which flags you set:
MODE 1 — Note (Notiz): Just provide title + body. No special flags needed. Example: log a call note after a conversation.
MODE 2 — To-do (Aufgabe): Set is_reminder: true + due_date. Example: "remind me to call Herr Müller back tomorrow"
MODE 3 — Appointment (Termin): Set is_event: true + starts_at + ends_at. Example: "schedule a viewing at Musterstr 12 at 3pm"
MODE 4 — Cancellation (Absage): Set reservation_reason_id to a valid reason. Example: "cancel deal — buyer withdrew financing"
Always link tasks to contacts/properties/projects via the *_ids arrays so they appear in the correct activity feeds.
The body field accepts HTML content.
create_webhookCreate a webhook to subscribe to Propstack CRM events.
Propstack will POST a JSON payload to target_url whenever the event fires. Use HMAC verification (secret in response) to validate payloads.
Common events:
Use this to set up automation triggers, e.g.: "Notify me when any property status changes" "Alert when a new contact is created"
delete_contactDelete a contact from Propstack CRM (soft delete).
The contact is moved to a 30-day recycle bin and can be restored.
Use this tool for:
delete_search_profileDelete a search profile from Propstack.
Use this tool when:
delete_webhookDelete a webhook subscription from Propstack.
Removes the webhook so Propstack will stop sending events to its URL.
full_contact_360Get a complete 360° view of a contact — everything you need before calling a client.
Combines 4 API calls in parallel:
Returns a complete contact dossier in one request. Use this when you need the full picture: "Tell me everything about Herr Weber."
Data minimization (Art. 25 DSGVO): pass 'fields' with an array of contact field names to limit the contact detail section to only those fields (e.g. ["first_name", "last_name", "email"]). The search profiles, deals, and activity sections are unaffected. Omit 'fields' for the full detail section. Unknown field names produce an error listing the valid options.
get_contactGet full details of a single contact by ID.
Use this tool to:
Use 'include' to load related data in one request.
get_contact_favoritesGet properties that a contact has favorited/bookmarked.
Returns the list of properties the contact has marked as favorites in Propstack. Use to understand which listings a buyer is most interested in.
get_contact_sourcesList all available contact/lead sources in Propstack.
Returns the list of sources like "Immobilienscout 24", "Website", "Empfehlung", etc. with their IDs.
Use this tool to look up valid source IDs before creating or updating contacts with client_source_id.
get_pipelineGet a single deal pipeline by ID with its stages.
Returns the pipeline with all stages in order. Use this when you already know which pipeline you need and want its stage details.
get_projectGet full details of a single project by ID.
Returns the complete project with all units, images, floorplans, documents, and links.
Use this tool to:
get_propertyGet full details of a single property by ID.
Use this tool to:
Always fetches with new=1 (extra fields) and expand=1 (custom fields).
get_property_statusesList all available property statuses in Propstack.
Returns statuses like "Verfügbar", "Reserviert", "Verkauft" with their IDs, colors, and sort positions.
Use this tool to look up valid status IDs before:
get_taskGet full details of a single task by ID.
Returns the task with all linked entities expanded (contacts, properties, projects, viewings) by default.
Use this tool to:
list_activity_typesList all activity/task types in Propstack.
These are templates for creating notes, todos (reminders), events, and messages. Each has an id, name, and category. Use these IDs when creating tasks:
Categories map to search_activities filter: for_notes→note, for_reminders→reminder, for_events→event, message→message.
list_contact_statusesList contact statuses (Kontaktstatus) in Propstack.
Use these IDs for search_contacts (status param) and create_contact/update_contact (client_status_id). E.g. "Lead", "Kunde", "Archiviert".
list_custom_fieldsList custom field definitions for an entity type in Propstack.
IMPORTANT: Call this tool to discover what custom fields exist before reading or writing custom field values on contacts, properties, etc.
Returns field groups, each containing field definitions with:
To READ custom fields: use expand=true on search or get tools. To WRITE custom fields: use partial_custom_fields: {"cf_field_name": "value"}. To FILTER by custom fields: add cf_fieldname=value as a search param.
list_documentsList documents attached to a property, project, or contact.
Documents include floor plans (Grundrisse), exposés, contracts, photos, and any other uploaded files.
Use this tool to:
Filter by exactly one of property_id, project_id, or client_id.
list_eventsList calendar events (Termine) in Propstack.
Events are appointments like property viewings, client meetings, notary appointments, etc.
Use this tool to:
Event states:
list_locationsList geographic areas/districts (Geolagen) in Propstack.
Returns location IDs and names used for property and search profile location matching. Use location IDs when creating search profiles or filtering properties by area.
list_pipelinesList all deal pipelines and their stages in Propstack.
Returns each pipeline with its ordered stages, including stage IDs, names, positions, colors, and chance percentages.
You NEED stage IDs from this tool to create or move deals. Call this before using create_deal or update_deal if you don't know the stage IDs.
Typical pipelines: Sales (Verkauf), Acquisition (Akquise), Rental (Vermietung). Typical stages: Anfrage → Besichtigung → Reserviert → Notartermin → Verkauft.
list_projectsList development projects in Propstack.
A project is a "super-object" that groups multiple property units (e.g. a new-build apartment complex with 20 units).
Use this tool to:
Use expand=true to include custom fields in the response.
list_reservation_reasonsList deal cancellation reasons (Reservierungsgründe/Absagegründe).
Use when creating deal cancellations (create_task with reservation_reason_id) or filtering lost deals (search_deals reservation_reason_ids).
list_search_profilesList search profiles (Suchprofile) in Propstack.
A search profile captures what a buyer or renter is looking for — cities, price range, room count, features, etc. Every search profile belongs to a contact.
Use this tool to:
Filter by contact ID to answer "What is this buyer looking for?"
list_tagsList all tags/labels (Merkmale/Gruppen) in Propstack.
Use these IDs to filter contacts (search_contacts group param) or assign tags (create_contact/update_contact group_ids). Filter by entity to get tags for contacts, properties, or activities.
Entity: for_clients (default), for_properties, for_activities.
Returns flat list: Name (ID: 123). Use super_groups param to optionally try hierarchical view via /super_groups.
list_teamsList all teams/departments in Propstack.
Returns teams with their broker member assignments. Use for team-level filtering and to understand the organizational structure.
list_usersList all brokers/agents (Nutzer) in the Propstack account.
Returns team members with their IDs, names, email, phone, position, team, and department assignments.
You need broker IDs for:
list_webhooksList all configured webhooks in Propstack.
Returns each webhook with its URL, subscribed events, active status, and HMAC secret. Use to review existing automation triggers.
match_contacts_to_propertyFind contacts whose search profiles match a property. Returns a ranked list with match scores.
Use when a new listing comes in to find potential buyers/renters: "Who should I send this new listing to?"
Logic:
pipeline_summaryPipeline overview — deals per stage, total values, and stale deals needing attention.
Fetches all deal pipelines and deals, then aggregates:
Filter by pipeline_id and/or broker_id. Use when asked: "How's the pipeline looking?" or "Give me a sales overview."
property_performance_reportPerformance report for a property — days on market, inquiry count, pipeline breakdown, and activity summary.
Combines 3 API calls in parallel:
Calculates: days on market, total inquiries, deals by stage/category, and recent activity breakdown by type.
Use when asked: "How is the Friedrichstr property doing?"
search_activitiesSearch the activity feed/timeline in Propstack.
Activities are the read-only feed of everything that happened: emails sent, notes logged, tasks created, events scheduled, cancellations, GDPR policy changes, etc.
Use this tool to:
Activity types:
Use list_activity_types to see all valid types for this account.
search_contactsSearch and filter contacts in Propstack CRM.
Use this tool to:
The 'q' parameter searches across: first name, last name, all emails, all addresses, and all phone numbers.
Phone search ('phone_number') ignores formatting — both 015712345678 and 0157-123-456-78 will match.
Returns paginated results. Use expand=true for full details including custom fields.
Custom fields: pass 'custom_filters' as an object of custom-field-name → value to filter by agency-specific fields (use list_custom_fields to discover field names). Each entry becomes a cf_<name> query parameter, e.g. { marketing_channel: "Website" }.
Data minimization (Art. 25 DSGVO): pass 'fields' with an array of contact field names to return only those fields per contact (e.g. ["first_name", "last_name", "email"]). Omit 'fields' to return the default set unchanged. Unknown field names produce an error listing the valid options.
search_contacts_by_phoneLook up a contact by phone number.
This is the go-to tool for voice agent caller identification. When a call comes in, use this tool with the caller's phone number to instantly find the matching contact.
Phone matching ignores formatting — all of these find the same contact: 015712345678, 0157-123-456-78, +49 157 12345678
Returns the matching contact(s) with key details. If no match is found, the caller is unknown and you should create a new contact.
search_dealsSearch and filter deals (contact↔property relationships) in Propstack.
Use this tool to:
A "deal" represents an interested contact linked to a property at a specific stage in a sales/rental pipeline (e.g. Anfrage → Besichtigung → Reserviert → Notartermin → Verkauft).
Use include="client,property" to get expanded contact and property details in one request.
Common queries:
Data minimization (Art. 25 DSGVO): pass 'fields' with an array of deal field names to return only those fields per deal (e.g. ["id", "deal_stage_id", "sold_price"]). Omit 'fields' to return the default set unchanged. Unknown field names produce an error listing the valid options.
search_propertiesSearch and filter properties (Objekte) in Propstack CRM.
Use this tool to:
The 'q' parameter searches: unit_id, street, zip code, city, district, exposé ID.
Range filter pattern: 11 numeric fields each have _from and _to variants. For example, price_from=200000 & price_to=400000 finds properties priced 200–400k. Available range fields: price, base_rent, total_rent, property_space_value, living_space, plot_area, number_of_rooms, number_of_bed_rooms, number_of_bath_rooms, floor, construction_year.
Common queries:
Custom fields: pass 'custom_filters' as an object of custom-field-name → value (use list_custom_fields to discover field names). Each entry becomes a cf_<name> query parameter, e.g. { energy_class: "A" }.
Always returns total count. Use expand=true for custom fields.
Data minimization (Art. 25 DSGVO): pass 'fields' with an array of property field names to return only those fields per property (e.g. ["id", "title", "price", "city"]). Omit 'fields' to return the default set unchanged. Unknown field names produce an error listing the valid options.
send_emailSend an email using a Propstack email template (snippet).
Propstack sends emails through connected broker email accounts. The broker_id determines which account sends the email. The snippet_id selects the email template to use.
Use this tool to:
Link the email to contacts, properties, and projects so it appears in the correct CRM activity feeds.
Important:
smart_lead_intakeComplete lead intake workflow — dedup check, create/update contact, log notes, create deal if specific property, and set follow-up reminder.
Perfect for post-call processing from a voice agent. Handles the entire intake in one tool call:
Returns what was done: created vs updated, IDs of all created records.
update_contactUpdate an existing contact in Propstack CRM.
Use this tool to:
Tag management options:
Only provide the fields you want to change.
update_dealUpdate an existing deal in Propstack.
Use this tool to:
Only provide the fields you want to change.
update_emailUpdate an email in Propstack.
Use this tool to:
Only provide the fields you want to change.
update_propertyUpdate an existing property in Propstack CRM.
Use this tool to:
Only provide the fields you want to change. Use get_property_statuses to look up valid status IDs.
update_search_profileUpdate an existing search profile in Propstack.
Use this tool to:
Only provide the fields you want to change.
update_taskUpdate an existing task in Propstack.
Use this tool to:
Only provide the fields you want to change.
upload_documentUpload a document to a property, project, or contact in Propstack.
The doc field must be a base64 data URI, e.g.: "data:application/pdf;base64,JVBERi0xLjQ..." "data:image/png;base64,iVBORw0KGgo..."
Attach to exactly one entity: property_id, project_id, or client_id.
Use the boolean flags to classify the document:
BEFORE YOU INSTALL
52 tools when we connected. The documentation heading says 49, but its tables name all 52. What each tool can do depends on the permissions of your Propstack API key.
All 3 documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 52 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npm install propstack-mcp-server{
"mcpServers": {
"propstack": {
"command": "npx",
"args": [
"-y",
"propstack-mcp-server"
],
"env": {
"PROPSTACK_API_KEY": "<YOUR_PROPSTACK_API_KEY>"
}
}
}
}MCP servers
raklapimenta
jbechtel-97
fdcommercial
ccedacero