Skip to main content
This documentation site is also an MCP server. Point your AI assistant at it and the assistant can search and read these pages on demand — so answers about the REST API and the MCP tools come from the current documentation rather than from whatever the model happens to remember.
No account, no key, no configuration. The documentation is public and so is this endpoint.

Two MCP servers, two jobs

Prophia runs two MCP servers and they are easy to mix up: They complement each other. Connect both and an assistant can look up how an endpoint works and then call it against your real portfolio. This page covers the docs server — the MCP server overview covers the one that reaches your data.

Connect your client

Claude Desktop and Claude on the web

1

Open connector settings

Open Settings → Connectors and choose Add custom connector.
2

Add the server

Name it Prophia Docs and enter https://docs.prophia.com/mcp.
3

Ask something

Try: “Using the Prophia docs, what does include=tags return?”
There is no sign-in step — unlike the Prophia MCP server, this one serves public content and never prompts for authorization.

Claude Code

Cursor

Open the command palette (⌘⇧P / Ctrl+Shift+P), run Open MCP settings, and add:

VS Code

Create .vscode/mcp.json in your workspace:

Any other client

The server speaks the MCP Streamable HTTP transport. Give your client the URL https://docs.prophia.com/mcp and no auth headers.
The AI menu at the top of every page on this site has one-click shortcuts — Copy MCP Server, Connect to Cursor, and Connect to VS Code — so you can add the server without retyping anything.

What a connected assistant can do

The server gives your assistant three abilities:
  • Search the whole documentation site and get back matching passages with their titles and links
  • Browse the site’s page tree — listing and reading pages in bulk rather than guessing at URLs
  • Report a problem with a page as incorrect, outdated, confusing, or incomplete. That feedback lands in our documentation analytics, so telling your assistant “this page is wrong about pagination” actually reaches us.
Assistants generally reach for these on their own once the server is connected. If yours doesn’t, naming the source usually settles it: “Check the Prophia docs first.”

Worth asking

  • “Using the Prophia docs, how do I page through more than 100 leases?”
  • “What does include=tags return, and what’s the catch with per-space values?”
  • “Write a Python function that fetches every lease in a building from the Prophia REST API, handling pagination.”
  • “Which Prophia MCP tools can write data, and what entitlement do they need?”
  • “What’s the difference between an account API key and a user API key?”

Without an MCP client

If your tool doesn’t speak MCP, the same content is available as plain text: The per-page AI menu also offers Copy page as Markdown and one-click handoffs to Claude and ChatGPT with the current page as context.

Automatic discovery

Clients that discover MCP servers on their own will find this one at:
You don’t need to visit it — it exists so that agents pointed at docs.prophia.com can locate the server without being handed the URL.