Google Analytics MCP for apartments: setup and use cases

A Google Analytics MCP connector is a server your AI assistant calls to read GA4 data when you ask a question in chat. Leasestory is one built for apartment marketing: it reads each community's Analytics, Search Console and Google Ads numbers through your own Google access, counts leads the way your reports do, and never writes anything back.

What a Google Analytics MCP connector does

MCP, the Model Context Protocol, is the open standard assistants use to reach outside tools. A connector sits at the other end: the assistant sends it a request shaped like your question, the connector answers with data, and the assistant writes the reply. The assistant never holds your Google password and never sees more than the connector returns.

This connector returns numbers the way the monthly report does. A lead is a tour request, a phone tap or a contact form, counted once, with GA4's "Create event" copies and page-view rules left out by name. Google Ads cost comes from GA4's Google Ads link, so it matches what Google Ads shows, and a campaign belongs to a community when its name contains the community's pattern. Ask without dates and it reads the 28 days ending yesterday.

What you need before you connect

• A paid plan. The connector comes with Agency and Agency + Brain. The free report shows one community's month, but it doesn't include the connector.
• The Google login you use for Leasestory. The owner or a team member signs in with it when the assistant asks, and the connection then belongs to the account.
• Budgets, for pacing questions. Each community's approved monthly ad budget, entered on Properties. Every other question works as soon as a property is switched on.

How to connect it in five steps

Today that's Claude on the web, the desktop app and Claude Code, all on one connection.

1. Copy the address. Sign in, open Settings, then MCP. The connector address is at the top with a Copy button. The same tab shows the terminal command and, later, every app you've connected.
2. Add a custom connector. In your assistant, open Customize, then Connectors, click Add, then Add custom connector. Name it, paste the address and click Continue.
3. Keep what it detects. The assistant reads the connector's sign-in settings on its own. Leave them as they are, choose Sign in now, and click Add.
4. Allow on the Leasestory page. A page opens under your Google login, or asks for it. It lists what the assistant will be able to do: see your properties, reports and action items, look up Google Analytics and Search Console numbers, and get download links. Click Allow.
5. Switch it on in a chat. In a conversation, open the + menu, choose Connectors and turn the connector on. Then ask the first question.

From a terminal. The command-line client in the line above takes one command, also on the Settings tab with a Copy button: claude mcp add --transport http leasestory https://leasestory.com/mcp. Then type /mcp in the session and sign in when the browser opens. The Leasestory page warns that it's sending access to a program on this computer; continue only if you just started it.

The assistant's own guide to custom connectors covers the same steps and the team plans, where an owner adds the connector to the organization before members connect it.

What your assistant can and can't do

• Read, from the start. Your properties, monthly reports and action items; Google Analytics, Search Console and Google Ads numbers; download links to report PDFs.
• Change, with your approval. Generate reports and send them to the Dropbox or Drive folders you've already connected, switch properties on or off and edit their settings, change the schedule, branding, logo and report notes, and give you a Stripe link for billing, where nothing changes until you confirm. The first time it tries to change something, the Leasestory page comes back asking you to allow changes, and the assistant checks with you before each one.
• Never. Delete your account or your reports, connect a new Dropbox or Google Drive, or change anything in Google Analytics, Search Console or Google Ads. Budgets are never changed from the assistant: it gives the number, a person sets it.

It only sees what your Google login can see, and it can't change anything in Google.

Use cases: eight questions to ask first

1. "Which communities are off pace this month?" Month-to-date spend against each community's approved budget, through today, and where each one is projected to land. A campaign whose name matches no community is listed, never added in, and the assistant offers to fix the pattern.
2. "What did each campaign cost per lead last month, search partners separately?" Cost beside the sessions and leads each campaign, network or day brought, with leads counted like the report. Leads from visits that didn't come from Google Ads are shown apart, not dropped.
3. "How many leads did each community get, by type and by channel?" Tour requests, phone taps and contact forms for the 28 days ending yesterday, split by channel, source, landing page, website or device, with every counted event and thank-you page named. Leads from data-center towns or outside the community's country are flagged, still counted. Add "for the last twelve months" and each month is counted the way that month's report was.
4. "Which of my GA4 key events count as leads?" The property's key events, its "Create event" and "Modify event" rules, enhanced measurement and custom dimensions, with what lead counting does with each. The audit from the key events post, in one question.
5. "I just changed a tag. Is the event firing?" GA4's Realtime view of the last 30 minutes, raw counts, while you open the page. The ten-minute check from the contact form post, with the assistant watching.
6. "What are renters searching to find this community?" Search Console queries and pages, branded and non-branded, month by month if you ask. Follow with "Is the floor plans page in Google's index?" and it inspects the address, up to five pages per question. Search Console runs two to three days behind GA4, so the assistant keeps the two apart.
7. "How much traffic came from ChatGPT, Perplexity or Reddit last month?" Sessions by source, filtered to the site's name, for any community. The question most monthly reports can't answer yet.
8. "Summarize last month's report for this community and read me the action items." The stored report's headline numbers and written analysis, the internal action items, and a download link for the PDF that works for ten minutes. "Put every community's month side by side" does the portfolio in one call, with no Google calls at all. With your approval, "Make last month's reports" starts a run; the files are stored, not sent, until you ask to deliver them.

Every answer names what it counted and what it left out, so the number can be checked. When a question would take more than one page of results, the assistant says what the page covers instead of adding it up.

How to disconnect

On Settings, then MCP, the Connected apps list shows each connection, whether it is read-only or read and changes, when it was connected and when it was last used. Disconnect stops its access at once. Nothing else changes, and your reports stay. On the assistant's side, Customize, then Connectors, then Remove takes the connector out of its list.

FAQ: Google Analytics MCP for apartments

What is MCP?

MCP, the Model Context Protocol, is the open standard AI assistants use to talk to outside tools. A connector is a server at the other end that answers the assistant's requests with data. Leasestory is one: a single address you add to your assistant, which then reads your properties, reports and Google numbers when you ask.

Does the connector change anything in Google Analytics or Google Ads?

No. It reads Analytics, Search Console and Google Ads through your own Google access and never writes to them. Budgets are never changed from the assistant: it gives the number, and a person sets it in Google Ads. Changes to the account's own settings need a second approval, then a yes before each one.

Do I need a paid plan to connect my assistant?

Yes. The connector comes with the Agency and Agency + Brain plans. The free report shows one community's month under your branding with no card, but it doesn't include the connector. A team member on a paid account connects the same way the owner does, with the Google login they use for the account.

Where does the data go?

To the assistant you connected, and only when you ask it something. What it reads is handled under your own agreement with the assistant's provider. The connector logs each request's tool, status and time against your account id, never the numbers, the emails or the property names, and the Connected apps list shows every app that can ask.

Can the assistant make and send reports?

With your approval. It can start a run for a finished month, show its progress, and give you download links to the PDFs. Runs it starts are stored, not sent: it delivers them to the Dropbox or Google Drive folders you have already connected only when you ask, and it can't connect a new folder itself.

The rule

Connect once, through your own Google access. Ask in plain words. Read what the assistant counted before you trust the number.