A1 Google Contacts MCP
A1 Google Contacts MCP lets an AI app manage Google Contacts through 19 tools: read/search/list contacts and groups, create/update/delete contacts individually or in batches, organize contacts with labels, sync changes, and work with auto-saved "Other contacts", plus a raw People API escape hatch.
Find and read contacts: list with pagination/sync tokens, prefix search, get by resource name, batch-get up to 200 contacts
Create and update contacts: single or batch create (up to 200), etag-guarded updates that replace field groups, clear fields with empty values
Delete contacts: permanent single or batch delete (up to 500), marked destructive
Manage groups/labels: list, get, create, rename, delete groups; add/remove members in one call; optionally delete contacts when deleting a group
Handle Other contacts: list/search auto-saved contacts, copy them into My Contacts
Sync support: sync tokens for incremental listing of contacts, groups, and Other contacts
Raw access: call any People API v1 endpoint (e.g. contact photos) via raw_request
Safety features: explicit read/write/destructive annotations, no auto-retry on ambiguous writes, search-index lag documented
Allows AI agents to manage Google Contacts via the Google People API, including searching, reading, creating, updating, and deleting contacts, organizing contacts with labels/groups, and working with automatically saved Other contacts.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@A1 Google Contacts MCPFind everyone from Acme in my contacts and show their emails and phone numbers."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Contacts MCP
English | Русский
A1 Google Contacts MCP lets an AI app manage your Google address book in plain language. Find a contact, create or update one, organize contacts with labels, run batch imports and clean-ups, and turn auto-saved "Other contacts" into real ones.
It uses the Google People API — the API behind Google Contacts — with your Google account. It guards every update against concurrent edits, keeps reads compact with explicit field masks and makes the limits of the People API explicit instead of implying that every contacts task is possible.
19 tools. List, search and read contacts, create, update and delete them one at a time or in batches, manage contact groups and membership, and reach "Other contacts".
Updates don't clobber. Every update is etag-guarded: if a contact changed elsewhere since it was read, the write fails instead of silently overwriting the concurrent edit.
Deletes are real. The People API has no trash; deleting a contact or group is permanent, and the server marks those tools destructive so your AI app can ask first.
Minimal Google scopes. It uses
contactsfor read/write —contacts.readonlyis enough for a read-only setup — pluscontacts.other.readonlyonly for "Other contacts", without broad account access.
Start with a read-only question:
Find everyone from Acme in my contacts and show their emails and phone numbers.
Connect the server · Explore use cases · Open technical documentation
See it work in a minute
You: Show my contact card for Jane Doe — email, phone and company.
Assistant: Finds the contact and shows the requested fields. Nothing changes.
You: Change her phone number to +1 415 555 0100 and add her to the "Clients" label.
Assistant: Shows the contact and the proposed change, then asks for confirmation before writing.
You: Confirm.
Assistant: Applies the etag-guarded update and the label. If the contact changed elsewhere in the meantime, the write fails instead of overwriting it.
Related MCP server: MCP Google Contacts Server
Contents
Quick start
You need Node.js 20+, a Google account and OAuth credentials from a Google Cloud project with the People API enabled.
Add the server to your AI app.
Ask the read-only question above.
In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y mcp-google-contacts@latest and environment variables GOOGLE_CONTACTS_CLIENT_ID, GOOGLE_CONTACTS_CLIENT_SECRET, GOOGLE_CONTACTS_REFRESH_TOKEN, then select Save and Restart.
From the command line:
codex mcp add google-contacts \
--env GOOGLE_CONTACTS_CLIENT_ID=your_client_id \
--env GOOGLE_CONTACTS_CLIENT_SECRET=your_client_secret \
--env GOOGLE_CONTACTS_REFRESH_TOKEN=your_refresh_token \
-- npx -y mcp-google-contacts@latestcodex mcp listclaude mcp add \
--env GOOGLE_CONTACTS_CLIENT_ID=your_client_id \
--env GOOGLE_CONTACTS_CLIENT_SECRET=your_client_secret \
--env GOOGLE_CONTACTS_REFRESH_TOKEN=your_refresh_token \
--transport stdio --scope user google-contacts \
-- npx -y mcp-google-contacts@latestclaude mcp listThe current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-contacts": {
"command": "npx",
"args": ["-y", "mcp-google-contacts@latest"],
"env": {
"GOOGLE_CONTACTS_CLIENT_ID": "your_client_id",
"GOOGLE_CONTACTS_CLIENT_SECRET": "your_client_secret",
"GOOGLE_CONTACTS_REFRESH_TOKEN": "your_refresh_token"
}
}
}
}In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Claude Desktop MCP documentation
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-contacts": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-contacts@latest"],
"env": {
"GOOGLE_CONTACTS_CLIENT_ID": "your_client_id",
"GOOGLE_CONTACTS_CLIENT_SECRET": "your_client_secret",
"GOOGLE_CONTACTS_REFRESH_TOKEN": "your_refresh_token"
}
}
}
}Run MCP: Open User Configuration and add:
{
"servers": {
"google-contacts": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-contacts@latest"],
"env": {
"GOOGLE_CONTACTS_CLIENT_ID": "${input:contacts_client_id}",
"GOOGLE_CONTACTS_CLIENT_SECRET": "${input:contacts_client_secret}",
"GOOGLE_CONTACTS_REFRESH_TOKEN": "${input:contacts_refresh_token}"
}
}
},
"inputs": [
{ "type": "promptString", "id": "contacts_client_id", "description": "Google OAuth client ID" },
{ "type": "promptString", "id": "contacts_client_secret", "description": "Google OAuth client secret", "password": true },
{ "type": "promptString", "id": "contacts_refresh_token", "description": "Google OAuth refresh token", "password": true }
]
}Check it with MCP: List Servers.
What you can ask it to do
Find and inspect contacts
Find everyone from Acme and show their emails and phone numbers.
Show who is in the "Clients" label.
List the contacts that changed since the last sync.
Keep the address book up to date
Create a contact for Jane Doe with her email, phone and company.
Update a contact's phone number or job title.
Import fifty people in one batch, or delete outdated contacts in one call.
Organize with labels
Create a "Clients" label and add these contacts to it.
Rename a label, or move a contact from one label to another.
Delete a label without deleting its contacts — or with them, but only when asked explicitly.
Work with "Other contacts"
Show the addresses Google saved automatically that are not in my contacts.
Copy one of them into My Contacts as a real contact.
How a contact changes
Every contact, group and Other contact has a full resource name (
people/c...,contactGroups/...,otherContacts/...); tools address records by it, exactly as the API returns it.Reads return only the fields named in the field mask (default: names, emails, phones, organizations, group memberships). An absent field may simply be outside the mask, not empty.
An update replaces each provided field group as a whole and is guarded by an etag: if the contact changed elsewhere since it was read, the write fails instead of overwriting the concurrent edit.
Deletes are permanent. The People API has no trash and no undo.
Search covers a cache that can lag recent writes by a few seconds and returns at most 30 results. "Other contacts" — addresses Google saves automatically — can only be read or copied into My Contacts, not edited in place. Contact photos have no dedicated tool; raw_request reaches those endpoints.
What can change
Operation | What happens | Confirmation boundary |
Read, search or batch-read contacts and groups | Reads contact data | No change |
Create a contact, a group or a batch of contacts | Adds records | Changes Google Contacts |
Update a contact or rename a group | Replaces the provided field groups, etag-guarded | Changes a contact |
Change label membership | Adds or removes a label on chosen contacts | Changes contacts |
Copy an Other contact | Adds a real contact to My Contacts | Changes Google Contacts |
Delete a contact, a group or a batch | Removes records permanently; deleting a group deletes its member contacts only when explicitly requested | Destructive |
Raw API request | Can call API methods without a dedicated tool | Potentially destructive |
The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.
Getting access
Google Contacts requires OAuth 2.0; an API key is not enough.
Create or select a Google Cloud project and enable People API.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Authorize the Google account whose contacts you want to manage. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.
Request the minimal scopes for what you use:
https://www.googleapis.com/auth/contacts https://www.googleapis.com/auth/contacts.other.readonly
contacts covers reading and writing contacts and groups; for a read-only setup contacts.readonly alone is enough. contacts.other.readonly is needed only by the "Other contacts" tools. A 403 on a single tool usually means the refresh token was minted without the scope that tool needs — re-consent with the missing scope added.
Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.
Configuration
Variable | Required | Description |
| Yes* | OAuth client ID. |
| Yes* | OAuth client secret. |
| Yes* | OAuth refresh token. |
| Yes* | Short-lived alternative to the OAuth trio (~1 h). |
| No | Google People API base URL override. |
| No | Per-request timeout; default |
| No | Temporary-error retries; default |
* Provide either the OAuth trio or an access token. With no credentials at all the server still starts and completes the MCP handshake; the first tool call then names the exact variables to set.
Data, limits and background work
Requests go to Google. The local server refreshes Google OAuth tokens and calls the People API at
people.googleapis.com. Its anonymous telemetry contains an installation ID, package version, AI client and platform versions, and tool names — never OAuth tokens, contact data, tool arguments or prompts. SetASKADS_TELEMETRY=0to opt out.Google quotas are per-user and low. The default People API quota allows roughly 90 reads and 90 writes per user per minute, so the batch tools beat loops of single calls; mutating batches must run one at a time. On
429the server backs off and retries; reads also retry after network and5xxerrors, while writes are not replayed after an uncertain failure.There is no background polling. The server runs only when called.
list_contactssupports sync tokens, so an AI app with scheduled tasks can periodically fetch only what changed; a sync token expires after about seven days, after which a full re-list is needed.
Technical documentation
MCP capability catalog — task-oriented pages for every tool.
Support
Found a bug or need a scenario? Create an issue or write in Telegram.
Maintenance
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and search Google Contacts through per-user OAuth authentication on serverless AWS Lambda. Provides read-only access to personal contacts with zero data storage and real-time API queries.832MIT
- AlicenseAqualityDmaintenanceProvides comprehensive Google Contacts management including creating, searching, and updating contacts with 25+ fields, managing contact groups, and accessing Google Workspace directories.191MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Google Calendar, Contacts, and Gmail through AI systems. Supports full CRUD operations including creating/updating/deleting events, managing contacts, sending emails, organizing with labels, and batch operations with OAuth2 authentication.129MIT
- AlicenseNot gradedqualityDmaintenanceGives AI assistants access to Google Contacts, supporting listing, searching, creating, updating, and deleting contacts, as well as searching Google Workspace directories.MIT
Related MCP Connectors
An AI-first personal CRM you run in natural language: contacts, reminders, notes, and more.
Streamline your Attio workflows using natural language to search, create, update, and organize com…
Connect AI to your Attio CRM. Manage contacts, companies, deals, and sales pipelines. Create tasks…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/A1-x-Tech/mcp-google-contacts'
If you have feedback or need assistance with the MCP directory API, please join our Discord server