Skip to main content
This page covers Claude Desktop and Claude Code. Other clients have their own page, and the MCP overview explains what a connected assistant can and can’t do.

What you need

  • A Prophia user account
  • Your organization’s API Name — the short identifier for your Prophia account that goes in the server URL
  • OAuth set up once for your organization — see OAuth setup. Already done? Continue below.
Your server URL is:
An admin on your Prophia account can copy both values from Account Settings → API/MCP Config: the MCP card shows API Name and Connection URL, each with a Copy button. That’s the surest way to get it right.
The API Name must match exactly — it’s a lowercase, hyphenated identifier (e.g. acme-real-estate) that may differ from your account’s display name, and it is case-sensitive. A wrong value will fail to connect.

Claude Desktop

1

Open connector settings

In Claude Desktop, open Settings → Connectors and choose Add custom connector.
2

Paste the server URL

Enter https://api.prophia.com/mcp/v1/{your-api-name} and save.
3

Sign in

The first time Claude uses a Prophia tool, a browser window opens and redirects to your organization’s own sign-in (Okta, Azure AD / Entra ID, Auth0, …). Sign in with your corporate credentials.
4

Choose what the connection can access

If your Prophia account uses role-based permissions, Prophia then shows the consent screen that every OAuth client goes through. Uncheck anything you don’t want Claude to use and click Allow Access. See Choosing what a connection can access.
5

Done

Claude now has access to your Prophia data. Try: “List the buildings in my portfolio.”
Claude Desktop requires the OAuth connection — it does not support API-key headers for this type of MCP server.

Claude Code (CLI)

On first use, a browser window opens for the same OAuth sign-in and, if your account uses role-based permissions, the same consent screen. Claude Code can alternatively connect headlessly with an API key — see API key access.

How the sign-in works

There is no client ID or secret to configure. The OAuth flow is fully discovery-driven: your MCP client discovers Prophia’s authorization endpoints, registers itself automatically, and completes an authorization-code + PKCE flow that hands login off to your company’s identity provider. Your Prophia permissions apply to every tool call — you can only see the data your Prophia user can see, and on accounts that use role-based permissions, only what you allowed on the consent screen.

Example prompts

  • “List all my Prophia accounts”
  • “What leases are in 100 Bayside Drive?”
  • “Find all rent escalation clauses in the Initech lease documents”
  • “Search for ‘force majeure’ across all documents at Bayside Corporate Center”
  • “Which leases had document changes in the last 30 days?”

Troubleshooting

Disconnect and reconnect the Prophia connector to re-authenticate.
The email returned by your identity provider must exactly match the email on your Prophia user account. If they differ, ask an admin at your organization — or Prophia Support — to reconcile them.
Check the URL and API Name (case-sensitive, exact match). If your organization hasn’t completed OAuth setup, the connection cannot start — the server returns not found until an identity provider is configured for the account.
Setting OAuth up and it isn’t working? The OAuth setup page has the admin-side checklist, in the order worth checking.