Anthropic's Claude can connect to Hummingbird property management software in about 40 minutes, with no software development background. The first endpoint to hit is the management summary report. How you run Claude after that is a spectrum: some operators sit down at the laptop they already own, and some put Claude on a spare machine they can talk to from their phone.
This guide is for operators who are not technical. It walks through the accounts you need, which Claude tool to pick, how to choose a setup style, and the exact order of steps. It is built from workflows independent operators are using in production, plus the current docs for Claude and for Tenant Inc.'s Nectar open API, the layer that exposes Hummingbird data to third-party tools.
The point is not that AI is clever. The setup is short once you know the order. Here is that order.
What Do You Need Before You Start?
Four things every operator needs, regardless of hardware:
- A paid Claude plan. Pro, Max, Team, or Enterprise. That unlocks Claude Cowork and Claude Code.
- A Hummingbird account with Nectar developer access. Nectar is Tenant Inc.'s open API. You will request API keys for your facilities through the developer portal.
- A free GitHub account. Create one at github.com if you do not have one. Many Claude Code and project setups ask you to sign in with GitHub, and it is the simplest way to keep a backup of the files Claude creates for you.
- A computer. That can be the laptop on your desk today, or a machine you dedicate to Claude. Both are valid. The section below helps you pick.
The API connection is the same either way. The hardware choice is about how you want to work with Claude day to day, not whether the Nectar keys work. For a deeper look at isolation and always-on tradeoffs, see our technical teardown of AI operations in self-storage.
What Setup Style Fits How You Want to Work?
Think in use cases, not one "correct" laptop.
| Setup | Who it fits | What you get |
|---|---|---|
| Everyday computer | You want to sit down, ask for a report, check numbers, then close the lid | Lowest friction. Use Claude Cowork or Claude Code on the machine you already own. Fine for learning the connection and for weekly or monthly reporting. |
| Same computer, scheduled jobs | You want Claude to produce a monthly PDF or nightly summary without you babysitting every step | Still your main machine, but leave it on when a job needs to run, or trigger work when you open the project. Good middle ground before buying hardware. |
| Dedicated always-on machine | You want a computer you can "talk to" from your phone, around the clock | Wipe an old laptop, keep it plugged in and online, run Claude Cowork there, reach it via Dispatch (Claude's phone-to-desktop feature), and keep TeamViewer or similar as a fallback. Strong choice if Claude is becoming an operations employee, not a desk tool. |
| Dedicated machine for isolation | You want a hard wall between the agent and your personal life | Same spare-computer setup, but the motive is security: only business logins and Nectar keys live on that box. Claude Cowork can control the computer it runs on, so isolation is a real upgrade when write access or always-on control is in play. |
Plenty of operators start on their everyday laptop, prove the management summary numbers, then move the same project folder onto a dedicated machine once they like the workflow. You are not locked into the first choice.
If you already know you want a machine you can text from the road, start on the spare computer. Just wipe it first, keep personal email and banking off it, and treat it like a staff workstation.
Which Claude Tool Should You Use?
Pick one wrapper. Do not install all three on day one.
| Tool | Best for | What it feels like |
|---|---|---|
| Claude Cowork | Least technical path; also the natural fit for an always-on spare machine | A desktop workspace. You describe the outcome in plain English. Claude can work with local files and, with Chrome paired, use a browser. |
| Claude Code in Visual Studio Code | A visual screen and chat panel | Install free VS Code, then the Claude Code extension from Anthropic. You talk to Claude in a side panel instead of a blank terminal. |
| Claude Code in Terminal | Comfortable pasting short commands | Open Terminal (Mac) or Command Prompt / PowerShell (Windows), type claude, and follow the prompts. Same engine as the VS Code extension, different wrapper. |
If you are not sure, start with Claude Cowork. If Cowork is not available on your plan or you prefer a chat panel next to files, use VS Code + Claude Code. Terminal Claude Code is fine too; it is just more intimidating the first time.
You are not locked in. The connection to Hummingbird is the Nectar API keys and the docs, not the window you typed into.
How Do You Get API Access to Hummingbird?
Do this before you open Claude.
- Go to Tenant Inc.'s Nectar developer portal (tenant.dev / nectar.tenantinc.com).
- Create a developer account if you do not have one.
- Ask your team (or Tenant support) for API keys scoped to one facility, with read access only.
- Keep those keys somewhere safe. You will paste them into Claude when it asks. Do not email them around or drop them in a shared Slack channel.
Nectar is the same connector that vendors like StoragePilot, Lumio, and Patchwork Labs use to read and write live Hummingbird data. Tenant Inc. opened that API to AI tools on July 13, 2026; the vendor pattern is the same one we covered in the StoragePilot Hummingbird integration. For an operator connecting their own AI, Nectar is what makes Claude see live occupancy and revenue instead of a stale spreadsheet export.
One store. Read only. Confirm the plumbing before you hand Claude your full portfolio or any write permission.
What Are the First 40 Minutes, Step by Step?
The connection itself is the fast part. Follow these moves in order on whichever computer you chose.
- Open the Claude tool you picked. Create or open a simple project folder for storage operations (something like
storage-opson the Desktop is fine). - Tell Claude, in plain English, what you want. Example: "I want to connect to my Hummingbird data through Tenant's Nectar API. Read the docs at https://nectar.tenantinc.com and tell me exactly what you need from me."
- Log into the Nectar developer docs in your browser so Claude (or you, copying from the page) can see the current endpoints and auth steps. Claude will list what it needs.
- Hand Claude the API keys when it asks. Paste them carefully. If Claude offers to save them in a local config file inside your project folder, that is normal. Do not put keys in a public GitHub repo. Keep the repo private.
- Ask Claude to hit the management summary report first. That report exposes occupancy, move-ins, move-outs, revenue versus budget, and web and phone leads. It is the highest-value first read in the system.
- If Claude asks you to run a short terminal command, copy it exactly, paste the result back, and keep going. That is the extent of "coding" for most operators.
- Confirm live data comes back for that one store. When Claude can show you the same occupancy and revenue figures you see in Hummingbird, the connection is done.
That is the 40 minutes. Everything after this is refinement, not connection.
How Do You Make Sure It Is Not Hallucinating?
Verify before you trust. This step is required.
Pull the same management summary report from Hummingbird yourself. Check Claude's numbers against it, line by line, for one period. Only after the numbers match should you expand scope.
Then give Claude memory. Have it read 12 months of management summary reports and build a small knowledge base so it remembers your baseline between sessions instead of starting from zero every time. Once one store is verified, adding more stores is mostly more keys: supply each facility's keys and confirm the data loads.
What Should You Build First, and What Comes Later?
Build the monthly report you actually want, then automate delivery. Reporting needs read access only, so it is the safest high-value starting point. Iterate with Claude until the report matches how you like to read it: by brand, rolled up to the portfolio, with fields like return on ad spend. Then schedule it. Claude can deliver a PDF by email (or another channel you approve) on a monthly cadence.
After that foundation is solid, three common additions:
- A market feed. Connect TractIQ through its official MCP connector so the monthly report includes rent-per-square-foot and supply pressure. Same pattern as in our piece on the TractIQ and CRED iQ AI data connector.
- Segmented reports. One KPI pack for the VP of operations, another for district managers, each on its own channel. Same data, different slice.
- Faster replies. Move from a scheduled "check every so often" job to a listener that answers when you text it. This is where a dedicated always-on machine often earns its keep.
Save write-back (changing rates, posting notes, touching tenant records) and customer-facing automation for last. Turn those on only with explicit permission, one task at a time.
The Setup Checklist Worth Saving
- Paid Claude plan, plus Claude Cowork or Claude Code (terminal or VS Code)
- Free GitHub account (keep any project repo private)
- A setup style you chose on purpose: everyday laptop, scheduled jobs on that machine, or a dedicated always-on / isolated computer
- Nectar developer account with API keys for one facility, read-only
- Claude pointed at the Nectar API docs; keys supplied only when asked
- First endpoint: management summary report
- Numbers checked by hand against the live Hummingbird report
- 12 months of history loaded once verification passes
- Write-back enabled deliberately, per task
- Full portfolio only after the single-store test works
Match the Setup to the Job
The connection is a 40-minute job. The judgment is choosing how Claude lives after that: a tool you open at your desk, a scheduled reporter on the same machine, or a spare computer you keep online and talk to from the road.
Start with one Claude tool, one store, and the management summary report. Verify the numbers with your own eyes, build the memory, then widen access. Move to a dedicated machine when the use case calls for it (always-on access, phone reachability, or isolation), not because a checklist said you had to. Operators who match the setup to the job get the payoff without inheriting risks from skipping the basics.
Sources
- Claude Cowork Overview, Anthropic
- Use Claude Code in VS Code, Anthropic
- Nectar Developer Portal, Tenant Inc.
- Nectar Data Connector, Tenant Inc.
- TractIQ Launches AI Connector, Bringing Verified Self-Storage Data Into Claude and ChatGPT, TractIQ