Google People
Connect Google profile, contacts, and directory data through Google's hosted People API MCP server.
You need a Google Cloud project and access to the Google Cloud console. To enable the People API, you need serviceusage.services.enable, normally through Service Usage Admin or Owner. To grant project roles, you need Project IAM Admin. Before you begin, have the application or security owner configure prompt and response screening for malicious content or prompt injection; Model Armor is one option.
Enable the People API
- Sign in to the Google Cloud console.
- In the console toolbar, use the resource selector to select the project that will own this configuration.
- Open APIs & Services > API Library.
- In Search for APIs & Services, search for
People API. - Open People API.
- Click Enable. If the API is already enabled, continue to the next section.
Grant MCP Tool User access
Repeat these steps for every person who will connect Google People.
- Open the project’s IAM page.
- Confirm that the same project is selected.
- Click Grant access.
- In New principals, enter the connecting user’s Google Account email.
- Click Select a role.
- Search for
MCP Tool User. - Select MCP Tool User.
- Click Save.
Configure the OAuth consent screen
Google does not allow an OAuth consent screen to be removed after it is configured. Confirm that you are using the intended project before continuing.
- Open Google Auth platform > Branding.
- If the page shows Google Auth platform not configured yet, click Get Started.
- Under App Information, enter
People API MCP Serverin App name. - Select a monitored User support email.
- Click Next.
- Under Audience, select Internal. If Internal is unavailable, select External.
- Click Next.
- Under Contact Information, enter a monitored Email address.
- Click Next.
- Under Finish, review the Google API Services User Data Policy with the application or security owner.
- With their approval, select I agree to the Google API Services: User Data Policy.
- Click Continue.
- Click Create.
If Google Auth platform was already configured, retain its approved Branding and Audience.
- Open Data Access.
- Click Add or Remove Scopes.
- Under Manually add scopes, paste these three scope URLs:
https://www.googleapis.com/auth/directory.readonlyhttps://www.googleapis.com/auth/userinfo.profilehttps://www.googleapis.com/auth/contacts.readonly
- Click Add to Table.
- Click Update.
- Click Save.
If you selected External and the app is in Testing, add every connecting account:
- Open Audience.
- Under Test users, click Add users.
- Enter each connecting user’s email.
- Click Save.
Create the OAuth client
- Open Google Auth platform > Clients.
- Click Create client.
- In Application type, select Web application.
- In Name, enter a recognizable name such as
Speakeasy AI Control Plane. - Under Authorized redirect URIs, click + Add URI.
- In URIs, enter
https://app.getgram.ai/mcp/remote_login_callback.
Prepare an approved secret store before the next step. The next dialog allows the client secret to be copied only once.
- Click Create. This opens OAuth 2.0 client created.
Copy the OAuth credentials
- In OAuth 2.0 client created, copy Client ID to the approved secret store.
- Under Client secrets, copy Client secret to the same store.
- Keep both values for connecting your credentials.
- Return to the Speakeasy AI Control Plane.
If you miss the one-time secret, delete it and create a new one before continuing.
Add the server in Speakeasy
- In the Speakeasy AI Control Plane sidebar, under Connect, select Sources.
- Click Add Source.
- Choose Custom remote server.
- On Add a custom remote MCP server, paste
https://people.googleapis.com/mcp/v1into Remote MCP server URL. - Click Add server.
This creates the hosted MCP server and opens its Overview page.
Connect your credentials
- From Overview, open Settings.
- Under Authentication, click Configure Manually or Use Discovered when offered.
- In Attach Remote Identity Provider, set Client Type to Manual.
- Confirm that Redirect URI matches
https://app.getgram.ai/mcp/remote_login_callbackentered when you created the OAuth client. - Paste the Client ID from the OAuth credentials.
- Paste the Client Secret (optional) from the OAuth credentials. Google requires this secret even though the field is labeled optional.
- In Scope (override), enter
https://www.googleapis.com/auth/directory.readonly,https://www.googleapis.com/auth/userinfo.profile,https://www.googleapis.com/auth/contacts.readonly. - Click Attach Identity Provider.
- At first connection, complete Google’s browser authorization with an account that has MCP Tool User access.
For billing, tool behavior, limits, and other details, see Google’s People API MCP documentation.