Side-by-Side Model Context Protocol Comparison
Propstack MCP vs Permisapi MCP
In-depth architectural comparison of the Propstack MCP and Permisapi MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Propstack MCP
Real Estate · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Permisapi MCP
Real Estate · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Propstack MCP if you need specialized Real Estate tools running via a local process. Choose Permisapi MCP if your workspace requires Real Estate integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Propstack MCP when:
- You need dedicated capabilities in the Real Estate domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
- You have access to required keys:
PROPSTACK_API_KEY. - Primary tools included: search_contacts, get_contact, create_contact.
Choose Permisapi MCP when:
- You need dedicated capabilities in the Real Estate domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Freemium).
- You have access to required keys:
PERMISAPI_KEY. - Primary tools included: search_permits, get_permit_details, fuzzy_search_addresses.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Propstack MCP Tools (52)
search_contacts
Search and filter contacts in Propstack CRM.
Use this tool to:
- Find contacts by name, email, or phone number
- List recent leads (sort by created_at desc)
- Find uncontacted leads (last_contact_at is null)
- Filter by broker assignment, status, tags, or GDPR status
- Search across all contact fields with 'q' parameter
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.
get_contact
Get full details of a single contact by ID.
Use this tool to:
- View complete contact information before a call
- Check relationships, documents, and owned properties
- See sub-contacts (e.g. family members at same address)
Use 'include' to load related data in one request.
create_contact
Create a new contact in Propstack CRM.
Use this tool to:
- Register a new lead after a phone call
- Create a contact from a web form submission
- Add a new property owner
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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Propstack MCP Configuration
Permisapi MCP Configuration