MLS Security Methods

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.lwolf.com/doc/cloud-cma/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "Cloud CMA MCP server": {
    "url": "https://apidocs.lwolf.com/doc/cloud-cma/mcp"
  }
}

Close
GET /docs/mls-security

Cloud CMA supports four security methods to ensure only valid, active MLS members access listing data via RETS integration.

Method 1: User RETS Credentials

Users provide their individual MLS RETS credentials. Cloud CMA stores credentials using RSA public key encryption and uses them to authenticate directly with the RETS server.

  • Pro: MLS has complete control; users can be deactivated immediately via normal MLS workflow
  • Con: Not all MLSs have RETS credentials set up for every member; manual setup may be required

Method 2: MLS RETS Credentials + Agent Verification

MLS provides Cloud CMA with RETS credentials. When users query data, Cloud CMA logs in with MLS credentials, then verifies the user exists and is active by querying the Agent/User table against their credentials.

  • Pro: MLS has complete control; users deactivated immediately
  • Con: MLS must allow querying on password field or return active member status

Method 3: Single Sign-On (SSO)

Users cannot log in directly at cloudcma.com. Instead, they log into their MLS system first, then access Cloud CMA via SSO link. Two options available:

  • Custom SSO: Parameters passed in URL (MLS code, user ID, secure hash, timestamp)
  • SAML: Cloud CMA is SAML certified and supports standard SAML providers
  • Pro: MLS controls both access to MLS and Cloud CMA; deepest integration with MLS systems
  • Con: MLS must set up the link/integration within their system

Method 4: Synchronized Agent Table

Cloud CMA maintains a synchronized table of currently active agents from the MLS. Users provide credentials which are verified against this table on each query.

  • Pro: MLS has complete control; users deactivated immediately via normal workflow
  • Con: Requires maintaining synchronized agent data

All methods ensure that only valid, active MLS members can access listing data through Cloud CMA.

Responses

  • 200

    MLS Security Methods documentation

GET /docs/mls-security
curl \
 --request GET 'https://cloudcma.com/docs/mls-security?api_key=api_token_value'