A1 Google Contacts MCP
A1 Google Contacts MCP lets an AI app connect to Google Contacts and read, search, create, update, delete, organize, batch-manage, and copy contacts and labels through the Google People API.
Connect and manage Google OAuth from chat:
auth_status,setup_instructions,set_client,start_login,finish_login,logout.Read contacts:
list_contactswith pagination/sync tokens,search_contacts,get_contact, andbatch_get_contactsfor up to 200 contacts.Write contacts:
create_contact, etag-guardedupdate_contact,delete_contact, plus batch create/update/delete tools.Manage labels/groups: list, get with members, create, rename, delete groups, and add/remove group members.
Work with “Other contacts”: list/search them and copy them into saved contacts.
Use
raw_requestas an escape hatch for uncovered People API v1 calls, such as contact photos.
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 "Deploy 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 MCP Find 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.
25 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".
Connects from the conversation. Say "connect Google Contacts": the server walks you through the OAuth client, catches Google's redirect on
127.0.0.1with PKCE and keeps the tokens itself — no config files, no restart.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 Workspace
Contents
Quick start
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
Add the server to your AI app.
Say "connect Google Contacts": the assistant walks you through creating the OAuth client and approving access without editing config files.
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 \
-- npx -y mcp-google-contacts@latestcodex mcp listclaude mcp add \
--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"]
}
}
}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"]
}
}
}Run MCP: Open User Configuration and add:
{
"servers": {
"google-contacts": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-contacts@latest"]
}
}
}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. There are two ways in, and the first one needs no configuration files.
Connect from the chat (recommended)
Say "connect Google Contacts" and the assistant runs the flow with you:
setup_instructionsprints the checklist: create or select a Google Cloud project, enable Google People API, configure the consent screen and create a Desktop app OAuth client.Download that client's JSON ("Download JSON") and give the assistant its path —
set_clientstores it owner-only. The secret never goes through the conversation.start_loginreturns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on127.0.0.1(PKCE), never through the chat.finish_loginexchanges the code and saves the tokens to~/.config/mcp-google-contacts/credentials.json(mode 0600) and verifies them with a real Google People API call — so an API that is still switched off is caught right there.
The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.
Environment variables (CI, unattended installs)
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
Every variable is optional — with none of them the server connects from the chat.
Variable | Required | Description |
| No* | OAuth client ID. |
| No* | OAuth client secret. |
| No* | OAuth refresh token. |
| No* | Short-lived alternative to the OAuth trio (~1 h). |
| No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
| 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. For each tool call it also sends the outcome and, on failure, an excerpt of the error text with e-mails, addresses, tokens, numbers of 4+ digits and quoted text replaced by#; a value from your request can appear in it if the error text contains it. 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.
Available Tools
25 toolsauth_statusGoogle connection statusARead-onlyIdempotent
Shows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected.
Inputs: no named parameters.
batch_create_contactsCreate many contacts at onceA
Creates up to 200 contacts in one call (People API people:batchCreateContacts). Each entry takes the same normalized fields as create_contact (name parts, emails[], phones[], addresses[], organization, birthday, notes, urls[]) and needs at least one. Returns createdPeople[] with each new resourceName. The call is atomic — a validation error anywhere creates nothing — but after an AMBIGUOUS failure (timeout/5xx; never auto-retried) the batch may still have committed: check via list_contacts before re-sending, or every contact gets created twice (the API has no duplicate detection). Send mutate batches sequentially, never in parallel — that is also how the per-user write quota stretches furthest.
Inputs: contacts (required), read_mask.
batch_delete_contactsDelete many contacts at onceADestructive
Permanently deletes up to 500 contacts in one call (People API people:batchDeleteContacts). There is no undo through this API — list the exact resource names first (batch_get_contacts shows what each one is) and treat the call as final. Returns an empty result on success; atomic per request. After an ambiguous failure (timeout/5xx; never auto-retried) check which contacts still exist via batch_get_contacts instead of re-sending — the deletes may have committed, and a second call then reports NOT_FOUND.
Inputs: resource_names (required).
batch_get_contactsGet many contacts at onceARead-onlyIdempotent
Fetches up to 200 contacts in one call (People API people:batchGet) — far cheaper against the tight per-user quota than a get_contact loop. Returns responses[], one per requested resource name IN THE SAME ORDER, each { requestedResourceName, status, person }; a missing contact gets a NOT_FOUND status in its own entry instead of failing the whole call, so check per-entry status. person_fields works exactly like in get_contact.
Inputs: resource_names (required), person_fields.
batch_update_contactsUpdate many contacts at onceADestructiveIdempotent
Updates up to 200 contacts in one call (People API people:batchUpdateContacts). Each entry names a contact (resource_name, optional etag — missing etags are auto-fetched in ONE extra batchGet read) plus the same normalized fields as update_contact. CAUTION — the API applies ONE shared update mask to the whole batch, computed here as the union of every entry's provided field groups: a group that one entry provides and another omits is CLEARED on the omitting entry. Safest is to give every entry the same set of fields; each provided group replaces its stored group as a whole, exactly like update_contact. Atomic per request; a stale etag fails the whole batch with 400 — re-read and retry deliberately, never blindly.
Inputs: updates (required), read_mask.
copy_other_contactCopy an Other contact into My ContactsA
Copies an 'Other contact' (from list_other_contacts) into the user's saved contacts — the only write that exists for Other contacts. copy_mask picks which fields carry over (names, emailAddresses, phoneNumbers; default all three). Returns the NEW saved person — use its resourceName ('people/c...') for further edits; the original otherContacts entry remains. Copying the same entry twice creates duplicate saved contacts. Requires BOTH the contacts and contacts.other.readonly OAuth scopes.
Inputs: resource_name (required), copy_mask, read_mask.
create_contactCreate a contactA
Creates a new contact in the account's Google Contacts and returns the created Person (resourceName, etag and the person_fields mask — use the resourceName for every later call). Provide any subset of the normalized fields: name parts, nickname, emails[], phones[], addresses[], organization, birthday, notes, urls[]; at least one is required. The API has NO duplicate detection — creating the same contact twice yields two contacts, so after an ambiguous failure (timeout/5xx; never auto-retried) check via search/list before re-sending. A just-created contact appears in list_contacts/get_contact immediately but reaches the search_contacts index with a delay. Contact photos need raw_request (updateContactPhoto).
Inputs: urls, notes, emails, phones, +10 more.
create_contact_groupCreate a contact groupA
Creates a new user contact group (label) and returns it (resourceName contactGroups/, name, etag). Group names must be unique — creating a duplicate name fails with 409 CONFLICT rather than making a second group. Put contacts into the new group with modify_group_members.
Inputs: name (required).
delete_contactDelete a contactADestructive
Permanently deletes one contact from the account's Google Contacts. There is no undo through this API (the Google Contacts UI keeps its own 30-day trash, but nothing here reads or restores it) — verify the resource_name with get_contact before deleting. Returns an empty result on success. After an ambiguous failure (timeout/5xx; never auto-retried) check with get_contact before re-sending: the delete may already have happened, and a second attempt then fails with 404.
Inputs: resource_name (required).
delete_contact_groupDelete a contact groupADestructive
Permanently deletes a user contact group (label). By default the member contacts SURVIVE — they only lose the label; delete_contacts=true also PERMANENTLY DELETES every contact in the group, so use it only when that is explicitly wanted (check the roster first via get_contact_group with max_members). System groups cannot be deleted. Returns an empty result on success; there is no undo through this API.
Inputs: resource_name (required), delete_contacts.
finish_loginFinish the Google loginAIdempotent
Second step: waits up to 20 s for the browser consent to finish, saves the tokens to an owner-only file and verifies the login with a read-only identity call, returning the account email and the granted scopes. After success every tool works immediately — no client restart. If the user granted only part of the requested permissions, the login is still saved and missingScopes lists what will not work. Logging in under a different Google account replaces the previous login (its refresh token is revoked best-effort) and the response carries previousAccountEmail so the change never goes unnoticed.
Inputs: no named parameters.
get_contactGet a contactARead-onlyIdempotent
Fetches one contact by resource name ("people/c...", or "people/me" for the signed-in user's own profile) with an explicit field mask. Returns a Person with resourceName, etag and the requested person_fields (default names, emailAddresses, phoneNumbers, organizations, memberships). The etag in the result is what update_contact needs to change this contact safely; memberships list the contact's groups as contactGroups/ resource names.
Inputs: resource_name (required), person_fields.
get_contact_groupGet a contact groupARead-onlyIdempotent
Fetches one contact group by resource name: name, groupType, memberCount and etag — plus, when max_members > 0, memberResourceNames[] with up to that many member contacts as people/ resource names (the only way the API returns a group's members; feed them to batch_get_contacts for details). The etag is what update_contact_group uses to rename safely.
Inputs: resource_name (required), max_members, group_fields.
list_contact_groupsList contact groupsARead-onlyIdempotent
Lists the account's contact groups (labels): contactGroups[] with resourceName (contactGroups/), name, groupType and memberCount, plus nextPageToken and totalItems. Two kinds come back: USER_CONTACT_GROUP (labels the user created — the only kind that can be renamed or deleted) and SYSTEM_CONTACT_GROUP (built-ins like contactGroups/myContacts and contactGroups/starred — fixed). group_fields defaults to metadata, groupType, memberCount, name; add memberCount explicitly if you narrow it and still want sizes. page_size up to 1000; sync_token works like in list_contacts (410 = expired, re-list in full).
Inputs: page_size, page_token, sync_token, group_fields.
list_contactsList contactsARead-onlyIdempotent
Lists the account's saved contacts (People API people/me/connections): connections[] of Person objects with resourceName, etag and the requested person_fields (default names, emailAddresses, phoneNumbers, organizations, memberships — an absent field may be unmasked, not empty), plus nextPageToken, totalItems and (when requested) nextSyncToken. page_size up to 1000 (default 100); paginate with page_token. For incremental polling set request_sync_token=true on a full listing, store nextSyncToken, and pass it as sync_token next time to get only changed/deleted people (deleted ones carry metadata.deleted=true); an expired token (~7 days) fails with HTTP 410 EXPIRED_SYNC_TOKEN — re-list without sync_token. Covers only the user's own saved contacts — not the Workspace directory and not auto-saved addresses (see list_other_contacts).
Inputs: page_size, page_token, sort_order, sync_token, +2 more.
list_other_contactsList or search Other contactsARead-onlyIdempotent
Lists 'Other contacts' — addresses Google auto-saved from the user's email interactions; they are NOT in the saved contact list and never appear in list_contacts/search_contacts. Give query to search them instead of listing (prefix match, max 30 results, no pagination — the warmup request is sent automatically before the session's first search); without query it lists with page_token pagination (page_size up to 1000) and optional sync tokens (request_sync_token/sync_token; expired ones fail with 410 — re-list in full). Only names, emailAddresses, phoneNumbers, photos and metadata exist here. Other contacts are read-only: to edit one, first make it a real contact with copy_other_contact. Requires the contacts.other.readonly OAuth scope — a 403 means the refresh token was minted without it.
Inputs: query, page_size, read_mask, page_token, +2 more.
logoutDisconnect from GoogleADestructive
Revokes the stored token at Google (oauth2.googleapis.com/revoke) and deletes the local credentials file. Tokens supplied via env variables are NOT touched — remove them from the MCP client config manually; envTokenStillSet in the response says whether any are still in effect.
Inputs: no named parameters.
modify_group_membersAdd or remove group membersADestructiveIdempotent
Adds and/or removes contacts in a contact group (label) in one call — at least one of add/remove is required, together up to ~1000 names. Contacts are addressed by their people/ resource names. The HTTP 200 response is NOT a full success receipt — read it: notFoundResourceNames lists contacts that do not exist (their changes were skipped) and canNotRemoveLastContactGroupResourceNames lists contacts that could not leave their last group. Removing a contact from a group never deletes the contact, and re-running the same call converges. Contacts cannot be removed from contactGroups/myContacts this way.
Inputs: resource_name (required), add, remove.
raw_requestRaw Google People API callADestructive
Escape hatch to call any Google People API v1 path directly, for requests the typed tools don't cover — e.g. contact photos (PATCH "v1/people/:updateContactPhoto" with {"photoBytes":""} or DELETE "v1/people/:deleteContactPhoto"), "Other contacts" (GET "v1/otherContacts?readMask=..." — needs the contacts.other.readonly scope on the token), or extra query parameters like sources. The path may carry a query string; repeated parameters are written inline ("v1/people:batchGet?resourceNames=people/a&resourceNames=people/b&personFields=names"). The Bearer token is added automatically; the method defaults to GET. Writes are never retried after ambiguous failures.
Inputs: path (required), body, method.
search_contactsSearch contactsARead-onlyIdempotent
Searches the account's saved contacts by prefix match on names, nicknames, emails, phones and organizations (People API people:searchContacts). Returns results[] of { person } with the requested read_mask fields. Max 30 results, no pagination — this is a quick lookup, not an export; use list_contacts to enumerate everything. The search index lags writes by seconds to minutes: a contact created or updated moments ago may be missing here even though list_contacts and get_contact already see it (the documented cache-warmup request is sent automatically before the session's first search, but the lag is server-side). Searches only the user's own saved contacts.
Inputs: query (required), page_size, read_mask.
set_clientSave the OAuth clientAIdempotent
Saves the OAuth client credentials from the JSON file downloaded from Google Cloud Console ('Download JSON' on a Desktop-app client). Pass the file PATH — the secret must never be pasted into the chat. The client is stored once in the shared ~/.config/mcp-google-auth/client.json (owner-only) and reused by every mcp-google-* server; tokens stay per-server. After this, call start_login.
Inputs: path (required).
setup_instructionsSetup instructionsARead-onlyIdempotent
Step-by-step checklist for connecting this server to Google: creating a Google Cloud project and a Desktop-app OAuth client, publishing the consent screen (mandatory — Testing-mode refresh tokens die after 7 days), downloading the client JSON and handing its PATH to set_client. Works without any credentials; the checklist shortens to 'enable the API + log in' when an OAuth client is already configured (one client serves the whole mcp-google-* line). Never asks the user to paste secrets into the chat.
Inputs: no named parameters.
start_loginStart the Google loginAIdempotent
First step of connecting from the chat, without editing config files or restarting the client. Returns authorizeUrl — show it to the user as a clickable link and ask them to open it in the browser ON THIS MACHINE, pick the Google account and approve access. A one-shot listener on 127.0.0.1 catches Google's redirect; the code is exchanged locally and never passes through the chat. Does not open the browser itself. The attempt lives 10 minutes; when the browser shows the success page, call finish_login.
Inputs: no named parameters.
update_contactUpdate a contactADestructiveIdempotent
Updates an existing contact and returns the updated Person. Only the provided fields are touched (updatePersonFields is computed automatically), but each provided field group is REPLACED AS A WHOLE: passing emails replaces all emails ([] clears them), passing any name part rewrites the whole name, and scalar fields clear on an empty value ("" for nickname/notes/birthday, {} for organization) — fetch current values with get_contact first and send complete groups, or data is silently dropped. Updates are etag-guarded: pass the etag from get_contact to fail cleanly (HTTP 400) if someone edited the contact meanwhile, or omit it and the current etag is fetched automatically (one extra read; last-write-wins). At least one contact field is required.
Inputs: resource_name (required), etag, urls, notes, +12 more.
update_contact_groupRename a contact groupADestructiveIdempotent
Renames a user contact group (the only mutable group attribute). Etag-guarded like contact updates: pass etag from get_contact_group to fail cleanly on a concurrent edit, or omit it and the current etag is fetched automatically (one extra read). System groups (contactGroups/myContacts, starred, ...) cannot be renamed; the new name must stay unique (409 CONFLICT otherwise). Returns the updated group.
Inputs: name (required), resource_name (required), etag.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 25 tools
Each tool targets a distinct resource+action pair, and the descriptions explicitly carve out boundaries: search_contacts vs list_contacts (quick lookup vs full enumeration), list_contacts vs list_other_contacts (saved vs auto-saved), get_contact vs batch_get_contacts, and single vs batch mutations are all clearly separated. The six auth tools form a linear, non-overlapping setup flow (setup_instructions → set_client → start_login → finish_login, plus auth_status and logout).
The dominant pattern is consistent snake_case verb_noun (list_contacts, create_contact_group, batch_delete_contacts, modify_group_members). The only deviations are the noun-first auth tools (auth_status, setup_instructions) and the bare verb logout, but these are few and still readable, and the batch_* prefix is applied uniformly.
At 25 tools this sits at the heavy end of the rubric: 14 core domain tools (contacts, groups, other contacts) plus 6 auth/onboarding tools, 4 batch variants, and a raw_request escape hatch. Most tools are justified (batch variants exist for quota reasons, auth flow is necessary), but the surface is larger than the domain strictly needs.
Full lifecycle coverage exists for contacts (list/search/get/create/update/delete plus batch) and groups (CRUD plus member modification), and Other contacts are covered read+copy. Minor gaps: contact photo operations and any non-default query parameters are only reachable through the generic raw_request rather than typed tools, and Workspace directory contacts are explicitly out of scope.
Maintenance
Related MCP Connectors
A private address book your AI can search, update and import into.
An AI-first personal CRM you run in natural language: contacts, reminders, notes, and more.
Personal CRM for Claude. Contacts live as plain-text files in your own Google Drive.
Keeps your contacts in sync across Google, Microsoft, Apple and CardDAV, and cleans up duplicates.
Related MCP Servers
- 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.101 npmMIT
- AlicenseNot gradedqualityDmaintenanceGives AI assistants access to Google Contacts, supporting listing, searching, creating, updating, and deleting contacts, as well as searching Google Workspace directories.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage contacts with full CRUD, dedup, merge, import/export, sync with Google/Apple/CardDAV, and git-backed rollback.AGPL 3.0