Your whole business, on one page

A Google Cloud project and three APIs

Claude talks to Google through a small program that runs on your computer. Google won't let that program in with your password, so you make it its own login, called a service account. Google Cloud is free for this. You won't be asked for a card.

1. Go to console.cloud.google.com and sign in with the Google account you use for Google Analytics.
2. Click the project picker at the top left, then New Project. Name it something like claude-analytics and click Create.
3. Make sure your new project is the one selected in the picker. If you skip this, you'll turn things on in the wrong project.
4. Open the menu (three lines, top left), then APIs & Services, then Library.
5. Search Google Analytics Admin API, click it, and click Enable.
6. Back to Library. Search Google Analytics Data API, click it, and click Enable.
7. Back to Library. Search Google Search Console API, click it, and click Enable.

The service account and its key

1. Open the menu, then IAM & Admin, then Service Accounts. Click Create service account.
2. Give it a name you'll recognize, like claude-analytics. Click Create and continue.
3. On the role screen, leave Role empty. Click Continue, then Done.
4. Find the new service account's email address. It ends in iam.gserviceaccount.com. Copy it and save it somewhere, because you'll paste it twice in Part 3.
5. Click that email to open the account's page. Open the Keys tab, then Add key, Create new key, JSON, Create. A small file downloads.
6. Make a folder called claude-keys inside your Documents folder. Move the file there and rename it analytics-key.json. Don't leave it in Downloads. Claude reads it from this exact spot every time, so if you move it later, it stops working.

Give it access to your data

Everything in Google Cloud gave the service account a way in. It did not give it permission to see your data. Your analytics doesn't know this login exists yet, so you add it like you'd add an assistant.

In Google Analytics

1. Go to analytics.google.com. Click Admin (gear icon, bottom left).
2. Check you're on the property for the site you want. Under Property, click Property access management.
3. Click the plus, then Add users. Paste the service account email.
4. Leave the role on Viewer. It only reads, so that's all it needs.
5. Turn off Notify new users by email, since nobody reads that inbox. Click Add.
6. Have more than one site? Repeat this for each property you want Claude to see.

In Search Console

1. Go to search.google.com/search-console and pick your site.
2. Click Settings, then Users and permissions, then Add user.
3. Paste the same email and choose Full. Click Add. Restricted can miss some reports. Full can see everything but can't add users or change who owns the site.
4. Repeat for each site you want Claude to see.

Connect it to Claude

1. Click Start, type PowerShell, and open Windows PowerShell. Paste this line and press Enter. Wait until it says it's installed. Open Terminal. Paste this line and press Enter. Wait until it says it's installed.
   Install uv · WindowsCopy

   powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

   Install uv · MacCopy

   curl -LsSf https://astral.sh/uv/install.sh | sh

   This installs a small tool called uv. It runs both connectors and downloads anything else they need, so you don't install Python yourself.
2. Close PowerShell and open a new PowerShell window. Paste this and press Enter: Close Terminal and open a new Terminal window. Paste this and press Enter:
   Find the uvx path · WindowsCopy

   Get-Command uvx | Select-Object -ExpandProperty Source

   Find the uvx path · MacCopy

   which uvx

   It prints a path like C:\Users\YourName\.local\bin\uvx.exe. Copy it and keep it handy. It prints a path like /Users/yourname/.local/bin/uvx. Copy it and keep it handy.
3. In the Claude desktop app, open Settings, then Developer, then click Edit Config. A folder opens with claude_desktop_config.json highlighted. Right-click it, choose Open with, then Notepad.Right-click it, choose Open With, then TextEdit.
4. Check what's already in the file.

   If it's empty, or has nothing under "mcpServers", select everything, delete it, and paste the full block below.

   If you already have other connectors listed, don't delete them. Skip ahead to the entries-only block further down.

   Full config · WindowsCopy

   {
     "mcpServers": {
       "analytics-mcp": {
         "command": "C:\\Users\\YOUR_NAME\\.local\\bin\\uvx.exe",
         "args": ["analytics-mcp"],
         "env": {
           "GOOGLE_APPLICATION_CREDENTIALS": "C:\\Users\\YOUR_NAME\\Documents\\claude-keys\\analytics-key.json",
           "GOOGLE_PROJECT_ID": "your-project-id"
         }
       },
       "gscServer": {
         "command": "C:\\Users\\YOUR_NAME\\.local\\bin\\uvx.exe",
         "args": ["mcp-search-console"],
         "env": {
           "GSC_CREDENTIALS_PATH": "C:\\Users\\YOUR_NAME\\Documents\\claude-keys\\analytics-key.json",
           "GSC_SKIP_OAUTH": "true"
         }
       }
     }
   }

   Full config · MacCopy

   {
     "mcpServers": {
       "analytics-mcp": {
         "command": "/Users/YOUR_NAME/.local/bin/uvx",
         "args": ["analytics-mcp"],
         "env": {
           "GOOGLE_APPLICATION_CREDENTIALS": "/Users/YOUR_NAME/Documents/claude-keys/analytics-key.json",
           "GOOGLE_PROJECT_ID": "your-project-id"
         }
       },
       "gscServer": {
         "command": "/Users/YOUR_NAME/.local/bin/uvx",
         "args": ["mcp-search-console"],
         "env": {
           "GSC_CREDENTIALS_PATH": "/Users/YOUR_NAME/Documents/claude-keys/analytics-key.json",
           "GSC_SKIP_OAUTH": "true"
         }
       }
     }
   }

   Already have connectors? Paste only these two entries inside your existing "mcpServers": { } section. Put a comma after the closing } of the entry right before them.

   Entries only · WindowsCopy

       "analytics-mcp": {
         "command": "C:\\Users\\YOUR_NAME\\.local\\bin\\uvx.exe",
         "args": ["analytics-mcp"],
         "env": {
           "GOOGLE_APPLICATION_CREDENTIALS": "C:\\Users\\YOUR_NAME\\Documents\\claude-keys\\analytics-key.json",
           "GOOGLE_PROJECT_ID": "your-project-id"
         }
       },
       "gscServer": {
         "command": "C:\\Users\\YOUR_NAME\\.local\\bin\\uvx.exe",
         "args": ["mcp-search-console"],
         "env": {
           "GSC_CREDENTIALS_PATH": "C:\\Users\\YOUR_NAME\\Documents\\claude-keys\\analytics-key.json",
           "GSC_SKIP_OAUTH": "true"
         }
       }

   Entries only · MacCopy

       "analytics-mcp": {
         "command": "/Users/YOUR_NAME/.local/bin/uvx",
         "args": ["analytics-mcp"],
         "env": {
           "GOOGLE_APPLICATION_CREDENTIALS": "/Users/YOUR_NAME/Documents/claude-keys/analytics-key.json",
           "GOOGLE_PROJECT_ID": "your-project-id"
         }
       },
       "gscServer": {
         "command": "/Users/YOUR_NAME/.local/bin/uvx",
         "args": ["mcp-search-console"],
         "env": {
           "GSC_CREDENTIALS_PATH": "/Users/YOUR_NAME/Documents/claude-keys/analytics-key.json",
           "GSC_SKIP_OAUTH": "true"
         }
       }

5. Swap in your own details. Three things, in four places:
   • The uvx path goes on both "command" lines. Use the path you copied in step 2.
   • Your key file path goes on both credentials lines. In File Explorer, open your claude-keys folder, right-click the key file, and choose Copy as path. Paste it in and delete the extra quote marks it brings.In Finder, open your claude-keys folder, right-click the key file, hold the Option key, and choose Copy "analytics-key.json" as Pathname.
   • Your project ID replaces your-project-id. In Google Cloud, click the project picker at the top and copy the ID next to your project's name, not the name itself. It's usually the name plus some numbers.
   Windows: double every backslash. A path like C:\Users\Dee has to be typed as C:\\Users\\Dee in this file. One missing backslash is the most common reason this file fails.
   Mac: paths use forward slashes, and nothing gets doubled.

   Keep the quote marks around every path. You need exactly one set, not two.

6. Save with Ctrl+S. Then fully quit Claude: click the up arrow by the clock, right-click the Claude icon, and choose Quit. Closing the window isn't enough. Open Claude again. Save with Command+S. Then fully quit Claude with Command+Q. Closing the window isn't enough. Open Claude again.
7. Go to Settings, then Developer. You should see analytics-mcp and gscServer both showing as running. The first start can take a minute while uv downloads what it needs.
8. Open a new chat and test it with these, one at a time. Click Allow when Claude asks to use a connector.
   Test 1Copy

   List my Google Analytics properties.

   Test 2Copy

   How many sessions did my site get last month, by channel?

   Test 3Copy

   What were my top 10 Search Console queries last month, with clicks and average position?

   If you have more than one site, Claude lists them all. Tell it which one you mean by name.

Turn on traffic in your dashboard

Your dashboard can't call the Google connectors directly, because they run on your computer. That's fine, because traffic doesn't need to be live. Once a month, the monthly save runs on this computer, reads Google Analytics, and saves the month to your history base: page views, sessions, and the views on each sales page. The Traffic panel reads from there.

1. In the Claude desktop app, on this same computer, run setup (or ask it to add traffic if your dashboard already exists). Tell it Google Analytics is connected and you want traffic.
2. It asks for the sales page for each offer. Use the page people read before they buy. If you sell from an all-in-one checkout like ThriveCart or Stan, where the checkout page is the page people read, use that one.
3. Give the full address, with the subdomain if there is one.
4. When it offers to schedule the monthly save, say yes. That task has to run on this computer too.

If your computer is off on the 2nd, open a chat any day that month and type:

Traffic troubleshooting

It's almost always one of these, in order of how often they come up.