DarakPlatform
Use casesDocsGuidesPricing
DocsGuides
Guides

Start here

  • Quickstart
  • Authentication

AI & MCP

  • Connect an AI assistant
  • Build with Darak and AI

About the data

  • What a listing is
  • Coverage and freshness

Building with it

  • Searching and filtering
  • Webhooks
  • Keeping a copy in sync

Operating

  • Limits and quotas
  • Pagination
  • Retrying safely
  • Errors
  • Versioning

Policies

  • Terms in practice

API reference →

Connect an AI assistant

Darak's read-only MCP service is at https://mcp.darak.app/mcp. Use the Streamable HTTP transport in an MCP client. The old https://darak.app/mcp address is retired; change existing client configurations and reconnect instead of following a redirect.

Claude Code

claude mcp add --transport http darak https://mcp.darak.app/mcp

Claude Desktop

If your client needs a local bridge for remote HTTP servers, add this to its MCP configuration and restart it:

{
  "mcpServers": {
    "darak": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.darak.app/mcp"]
    }
  }
}

Other clients

In Cursor or another client that supports remote Streamable HTTP MCP, add a remote server with URL https://mcp.darak.app/mcp. Client menus vary by version. Clients must support OAuth 2.1 with S256 PKCE to connect an account; don't assume every AI app supports remote MCP or the same sign-in flow. Ask it to call list_neighborhoods followed by search_listings to confirm the connection.

Signing in. Every call needs a Darak account. On the first request the server answers with a Bearer challenge; the protected-resource metadata names https://mcp.darak.app/mcp as the resource, darak.read as the scope, and https://darak.app/api/auth as the authorization-server issuer. The client discovers the authorization, registration and token endpoints from that issuer and opens Darak sign-in. You then choose which organization the connection uses (a new account creates a free one in the same flow) and approve the requested access. Calls count against that organization's plan, exactly like its API keys, and appear in its usage and request logs. Every plan can use all of the MCP server's tools: market statistics, valuations and projects that a plan's API keys don't include are available through MCP up to 1,000 units a month (they still count toward the plan's quota), and past that a tool answers with an upgrade link. Access tokens last an hour and refresh tokens up to a week. Do not paste an API key into an AI client's MCP configuration.

Troubleshooting. A 401 challenge with resource_metadata means the client should discover the issuer and offer sign-in. If it keeps using the old resource or a cached token, remove and re-add the server at the new URL. If OAuth is unsupported, use an MCP-compatible client; do not send a DPoP token as Bearer. If a connected call fails on scope or plan limits, check the organization's usage and request logs or contact [email protected].