Skip to main content
The Prophia MCP server works with any client that supports the MCP Streamable HTTP transport. The configuration is always the same three values:
  • Server URL: https://api.prophia.com/mcp/v1/{your-api-name} — an admin on your Prophia account can copy this from Account Settings → API/MCP Config
  • Transport: Streamable HTTP
  • Auth: OAuth (discovered automatically) or an API key header
For OAuth connections, your organization needs the one-time OAuth setup first, and your corporate email must match your Prophia user email exactly. An API key needs neither.

Cursor

  1. Open Cursor settings and navigate to the MCP section.
  2. Add a new server:
    • Name: Prophia
    • Type: Streamable HTTP
    • URL: https://api.prophia.com/mcp/v1/{your-api-name}
  3. On first use you’ll be prompted to authenticate in your browser via your organization’s sign-in. If your account uses role-based permissions, you then choose what Cursor can access on the consent screen, the same one every OAuth client gets.

Generic client configuration

For clients configured with a JSON file:
With OAuth, the client discovers Prophia’s authorization endpoints automatically and walks you through login, then through the consent screen if your account uses role-based permissions — there is no client ID or secret to paste. If your client can’t drive a browser login, use an API key instead.

Staying connected

How long you stay signed in depends on how your client registers with Prophia, which it does on its own the first time you connect:
  • A client that registers with a client secret (token_endpoint_auth_method of client_secret_basic or client_secret_post) gets refresh tokens and stays connected without signing in again, up to your organization’s maximum connection lifetime.
  • A client that registers without one (none) asks you to sign in again whenever its 12-hour access token expires.
See How long a connection lasts for the details.