closecadence-mcp

Use your Close Cadence real-estate tools from your own Claude. This is a tiny MCP server that lets Claude (Desktop / Code) call your Close Cadence tools — listings, CMAs, social, follow-ups, flyers, photo enhancement — directly, in your saved voice, on your plan's credits.

It's a thin client: it only forwards your authenticated requests to closecadence.ai. No tool logic or data lives in this package.

Setup (about 1 minute)

1. Get your key in the portal → API key (format cck.cus_….…).
2. Add this to your Claude config (Claude Desktop → Settings → Developer → Edit Config):

{
  "mcpServers": {
    "closecadence": {
      "command": "npx",
      "args": ["-y", "closecadence-mcp"],
      "env": { "CC_API_KEY": "cck.PASTE_YOUR_KEY" }
    }
  }
}

3. Restart Claude. Now ask things like "write a just-listed package for 412 Bayview Dr, $1.15M, 4-bed ocean view" — Claude uses your tools, in your voice.

Tools

• cc_listing, cc_cma, cc_social, cc_email, cc_followup, cc_market_report, cc_open_house, cc_prospecting, cc_listing_presentation
• cc_comps, cc_property (property data) · cc_flyer, cc_enhance (media)
• cc_list_tools (what's on your plan) · cc_run (any tool by id)
• Partner-spec aliases (2026-06-23 connector spec): generate_listing_doc (= cc_listing), generate_cma (= cc_cma), create_custom_video (listing-tour video script/storyboard; rendered video pending Creatomate/HeyGen keys), list_assets (your recent generated outputs), job_status (poll an async job by id)

If your membership lapses or you run out of credits, the tools say so clearly and point you to the portal.

Develop / test

npm install
npx @modelcontextprotocol/inspector node src/index.js   # set CC_API_KEY in env first

Point CC_API_BASE at a preview deploy to test against staging.

Publish (maintainers)

npm publish --access public (requires npm auth). After publishing, the portal's "Use in your own Claude" config (npx -y closecadence-mcp) works as shown above.