Skip to main content
Prophia exposes your portfolio data through two integration surfaces. Both are hosted by Prophia, both are read-optimized views of the same underlying data, and both scope everything to an account.

Choose your surface

MCP Server

Connect AI assistants (Claude, Cursor, any MCP client) to your Prophia data. Best when a person is asking questions in natural language.

REST API

Versioned JSON API for programmatic integration — sync leases into your data warehouse, feed your BI stack, automate reporting.

The account scope

Every request — MCP or REST — operates inside one account:
  • REST paths embed the account id: /rest/v2/accounts/{accountId}/properties
  • The MCP URL embeds your account’s API Name: /mcp/v1/acme-real-estate
Your credentials determine which accounts you can reach, and per-resource permissions (property, lease, document, tag) apply underneath — two users connected to the same account can see different data. Both surfaces expose the same hierarchy you see in the web application, so if you know where something lives in Prophia you know where to find it here. The data model page has the entity diagram, field conventions, and how tags reference spaces by suite name.

Getting started

Authentication

API keys, what each type can reach, and how to send them.

MCP server

What a connected assistant can do, and how to connect one.
There is a third, separate MCP server that serves this documentation rather than your data — public, no credentials, and useful alongside either surface above. See Connect AI to these docs.