Use Put Roots from inside Claude or ChatGPT

One address

https://www.putroots.com/mcp

claude.ai / ChatGPT: add it as a custom connector. Paste the address exactly as written — it is matched character for character.

Claude Code:

claude mcp add --transport http putroots https://www.putroots.com/mcp

Authorization is standard OAuth: you sign in with your Put Roots account on our page, see exactly what the connection will read, and can revoke it any time from Permissions I've granted.

What it can answer

• Search listings — our SF inventory, each listing with where it came from, when we fetched it, and whether the landlord wrote any requirements at all. Works without an account (a free sample; sign in for the full set).
• Can I qualify for this one? — a listing's written requirements against your file, line by line: what the landlord wrote, what you filled in, and the gap — with the landlord's original sentence. Asks you to sign in, because it compares against your qualifications.
• Bank, card, phone plan, SSN — the routes that work without an SSN, with branch addresses, hours, and the date each answer was checked. Works without an account.
• Start my move — hands you a sign-up link with your move date and new address pre-filled, so the 60-day plan starts from what you already told the assistant. It creates nothing until you open the link and sign up yourself. Asks you to sign in.

Three rules travel with every answer: it never says "you will / won't get it" — that is the landlord's call; "the landlord didn't write it" is an answer, not a blank; and every fact carries its source and date.

What sits behind these tools

An agent that runs a 60-day move for the renter: 40+ tasks across seven stages, each one approved by the renter before anything goes out. Today, in production: picks a no-SSN bank; ranks listings by the landlord's own written rule; sends three quote requests to movers, storage and cleaners; writes the notice to the old landlord; cancels internet and gym; confirms movers and the key pickup the day before; pre-opens internet and utilities; fills forms to the last field on ISP, DMV, USCIS and insurance sites; picks a gym, dentist and vet on the map and calls them; builds the first furniture cart; chases the deposit. The connector exposes the reading half of that; the REST API below exposes the partner half.

Read-only, by design

The connection reads our answers. Acting in your name — writing to a landlord, making the call, chasing the follow-up — only happens inside Put Roots, and only when you press send. The one thing it can "start" is a link you still have to open. That boundary is the point: the reading half can go anywhere; the acting half stays home.

For partners and developers: the same thing as an API

Everything the connector can do, and the partner-only operations, come from one table. It is served three ways:

• MCP — this page. For people using Claude, ChatGPT or their own agent.
• REST — https://www.putroots.com/v1/, described by /v1/openapi.json (OpenAPI 3.1). For listing sites, property managers, movers and anyone running a platform rather than an assistant.
• Outbound — for movers, storage and cleaning companies we push a signed JSON lead to your CRM endpoint the moment a renter approves their quote request, in addition to the email they send you.

Getting a key: POST /v1/partners with the form in the OpenAPI doc (code, name, kind, stages, contact email; providers also say their service and how to deliver). The key is shown once. Keys are scoped by journey stage: core for everyone, then rental_readiness, move_intake or life_setup by the stages you register for.

curl -X POST https://www.putroots.com/v1/partners \
  -H 'Content-Type: application/json' -d '{
  "code": "acme-movers-test", "name": "Acme Movers",
  "kind": "provider", "service": "movers",
  "stages": ["move_planning"], "contact_email": "you@acme.example",
  "delivery": { "intake_email": "leads@acme.example" }, "test": true }'

Sandbox first, no waiting: register with "test": true and the pr_test_ key you get back works immediately, with no approval step. It runs dry: leads come back redacted, real leads are never delivered to it, nothing is recorded, hand-offs are not billable. When your side works, register your production code separately (a code can only be registered once, and its key type is fixed at registration) without the flag: that pr_live_ key answers 403 pending_approval until we approve you by email, within 1 business day.

Affiliate providers (insurers, ISPs, mobile carriers): put your full tracking link in delivery.affiliate_code; when it is your only delivery, config.vendor (the vendor name our task graph uses for you) is required. The agent opens that link as the entry when it does the task for a user, and each open shows up as link_out in GET /v1/events.

Testing your integration: POST /v1/leads/sample sends one fictitious, signed lead to your registered endpoint or intake email, exactly as a real one would arrive.

What a partner never gets: a renter's line-by-line qualification (that is the renter's own, by the connector only), names or addresses on a test key, or any other partner's users. Errors are plain: 401 no key, 403 pending / revoked / wrong scope, 404 not yours, 429 with Retry-After.