360 Secure SkillHub
360 安全技能中心

CREA DDF MCP

核心功能为通过合规MCP服务器和CLI查询CREA/REALTOR.ca的DDF数据,可实现房产检索、单房产详情、元数据查看及媒体访问,支持配置限流、重试等参数。典型场景包括机构房产研究、Claude MCP/OpenClaw集成、脚本化自动化分析。输入需先配置凭证环境变量,通过CLI命令或工具调用触发;输出为结构化房产数据、元信息及媒体资源,需遵守合规要求。

danielfoch
danielfoch
热度 35.04
最近更新 2026-05-11 17:28:11
分类:开发依赖:代码执行 / MCP 服务 / 第三方 API应用场景:API 集成 / 数据处理 / 自动化脚本

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add crea-ddf-mcp
Metadata
name
crea-ddf-mcp
description
Query CREA/REALTOR.ca DDF via a hardened MCP server and CLI for institutional-grade listing data retrieval, metadata inspection, and media access. Use when a user needs DDF tools in Claude MCP, OpenClaw, or scripted research workflows.

CREA DDF MCP

Use this skill to run DDF as a governed MCP/CLI integration for downstream analysis and automations.

Workflow

1. Configure DDF credentials

Set environment variables:

  • DDF_BASE_URL
  • DDF_AUTH_URL
  • DDF_TOKEN_GRANT (client_credentials or password)
  • DDF_CLIENT_ID + DDF_CLIENT_SECRET (for client credentials)
  • DDF_USERNAME + DDF_PASSWORD (for password grant)

Optional operational controls:

  • DDF_HTTP_TIMEOUT_MS, DDF_HTTP_RETRIES, DDF_HTTP_RPS, DDF_HTTP_BURST
  • DDF_MEDIA_ENTITY, DDF_MEDIA_RECORD_KEY_FIELD, DDF_MEDIA_ORDER_FIELD

2. Build and run MCP

npm --workspace @fub/crea-ddf-mcp run build
node packages/crea-ddf-mcp/dist/mcp-server.js

3. Validate with CLI

npm --workspace @fub/crea-ddf-mcp run dev:cli -- search-properties --filters-json '{"city":"Toronto"}' --top 5
npm --workspace @fub/crea-ddf-mcp run dev:cli -- get-property --id "<ListingKey>"
npm --workspace @fub/crea-ddf-mcp run dev:cli -- get-metadata

4. Wire into Claude MCP/OpenClaw

Use references/claude-mcp-config.md for Claude setup and references/openclaw-wiring.md for OpenClaw runtime wiring.

Safety Rules

  • Prefer typed tools (ddf.search_properties, ddf.get_property) over raw calls.
  • Keep field selections to allowlisted safe sets unless governance is updated.
  • Treat data licensing/display obligations as upstream policy requirements.
  • Never store credentials in plaintext files committed to git.