Article
Create a Google Cloud Project for Claude Connectors
Set up one dedicated Google Cloud project to own the APIs, OAuth client, and quota for the Google MCP servers you connect to Claude.
Most local MCP servers for Google products, such as Google Analytics, Search Console, or Drive, call Google APIs with your own credentials. Those calls need a Google Cloud project behind them. The project is where the APIs are enabled, where your OAuth client lives, and where the quota is counted.
You could reuse a project you already have. I recommend creating one dedicated project for Claude connectors instead, for three reasons:
- Clear audit trail. Every API that a connector touches is enabled in one place, and nothing else depends on it.
- Easy to revoke. If you stop using the connectors, you can delete the project without affecting a real workload.
- No accidental reach. OAuth clients and test users for a personal tool should not sit next to production infrastructure.
This post creates that project. Later posts in the series enable APIs in it and connect individual MCP servers to Claude Code.
Before you start
You need:
- A Google account. A personal Gmail account works, and so does a Google Workspace account if your administrator allows you to create projects.
- Optionally, the Google Cloud CLI (
gcloud), if you prefer the terminal to the console.
You do not need a billing account. The Google Analytics Admin and Data APIs used later in this series work in a project without billing enabled.
Choose a name and a project ID
A project has three identifiers, and only one of them is yours to change later.
| Identifier | Example | Can it change? |
| --- | --- | --- |
| Project name | Claude Connector App | Yes, at any time |
| Project ID | claude-connector-4821 | No, it is permanent |
| Project number | 123456789012 | No, Google assigns it |
The project ID is the value you pass to gcloud and to MCP server configuration, so choose it deliberately:
- It must be 6 to 30 characters long, and globally unique across all of Google Cloud.
- It must start with a lowercase letter and contain only lowercase letters, digits, and hyphens.
- It cannot contain restricted words such as
googleorssl. An ID likegoogle-claude-connectoris rejected.
A short, descriptive prefix with a random suffix is usually enough, for example claude-connector-4821.
Option A: Create the project in the console
- Open the Google Cloud console and sign in with the account you will use with Claude.
- Open the project picker at the top of the page and select New project.
- Enter Claude Connector App as the project name.
- Select Edit next to the generated project ID and replace it with the ID you chose.
- For Location, keep No organization for a personal account. A Workspace account may require you to choose an organization or folder.
- Select Create, wait for the notification, and then select the new project in the project picker.
Option B: Create the project with gcloud
If you already have gcloud installed and signed in (gcloud auth login), one command creates the project:
gcloud projects create claude-connector-4821 --name="Claude Connector App" --labels=purpose=claude-connectors
The label is optional. It makes the project easy to find later with gcloud projects list --filter="labels.purpose=claude-connectors".
Make it the default project for future gcloud commands, and confirm that it exists:
gcloud config set project claude-connector-4821
gcloud projects describe claude-connector-4821
The describe output should show lifecycleState: ACTIVE. It also shows the project number, which some Google error messages use instead of the ID.
What will live in this project
Keep the project’s contents narrow and intentional. Over the course of this series, it holds:
- Enabled APIs, only the ones a connector actually calls. For example, the Google Analytics MCP server needs
analyticsadmin.googleapis.comandanalyticsdata.googleapis.com. - One OAuth consent screen, set to External with yourself as a test user.
- A Desktop app OAuth client, which lets
gcloudrequest Application Default Credentials for scopes that its built-in client cannot request.
It does not need service accounts or downloaded service account keys. For a personal setup, user credentials obtained through OAuth are simpler to manage and easier to revoke.
Keep it tidy
A few habits keep a utility project like this from becoming a liability:
- Check IAM & Admin → IAM occasionally. You should be the only principal, with the Owner role.
- Review what is enabled with
gcloud services list --enabled --project=claude-connector-4821, and disable APIs you no longer use. - Remove app access you no longer need from your Google Account at myaccount.google.com/permissions.
- When you are done with the connectors, run
gcloud projects delete claude-connector-4821. The project is shut down immediately and permanently deleted after about 30 days, during whichgcloud projects undeletecan restore it.
With the project in place, you can enable APIs in it and connect your first MCP server to Claude Code.
Related articles
Keep reading
Oct 26, 2026
Set Up the Google Analytics MCP Server in Claude Code on Windows and macOS
Connect Google's official Analytics MCP server to Claude Code with your own OAuth client and Application Default Credentials, so you can query GA4 data from the terminal.
Jul 14, 2020
Configuring Multiple GitHub Accounts in Windows Using SSH
A practical guide to keeping personal and work GitHub accounts side by side on Windows with separate SSH keys.
May 5, 2020
Integrating ESLint to VS Code
A quick walkthrough for setting up ESLint in VS Code for JavaScript or TypeScript projects.