Skip to main content
Advisor Connect is exposed at this protected resource identifier: 
https://mcp.brightplace.ai/mcp
MCP clients should use that value as the server URL and resource/audience value when OAuth is available.

​
Current access model

Advisor Connect accepts MCP requests without an Authorization header. This keeps launch clients simple while abuse controls remain active through aggregate, per-session, and per-tool rate limits. When a supported client sends a valid OAuth bearer token, BrightPlace Connect uses it for audit enrichment. The token can attach renter identity and client metadata to audit entries without changing the public tool contracts. Consent allows the AI client to call BrightPlace Connect tools during the conversation. It does not authorize the client to sign a lease, submit an application, contact a property outside the explicit tool flow, or act as a licensed broker.

​
Identity scopes

If your client shows identity scopes during sign-in, they may include:
ScopePurpose
openidEstablishes an authenticated identity.
emailAssociates the connection with an email address when available.
profileAssociates basic profile information when available.
Tool access is controlled by the server-side MCP tool surface documented here, not by publishing unrelated operator or bulk-data scopes.

​
Client guidance

  • Use https://mcp.brightplace.ai/mcp as the MCP server URL.
  • Treat OAuth as account-linking and audit attribution unless BrightPlace publishes narrower tool scopes later.
  • Show users the BrightPlace Privacy Policy and Terms of Service before or during account connection.
  • Never cache OAuth tokens in logs, prompts, analytics, or client-visible tool outputs.
  • Privacy Policy: https://www.brightplace.ai/privacy
  • Terms of Service: https://www.brightplace.ai/terms
  • Fair Housing commitment: https://www.brightplace.ai/fair-housing