Listed from the MCP registry; nobody on Odel publishes it.
MCP server for the Google People API: search, create, update and delete contacts and groups.
Runs on your machine from its package; the steps are below.

At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y mcp-google-contacts
MCP client config
{
"mcpServers": {
"google-contacts-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-google-contacts"
]
}
}
}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.
127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.contacts for read/write — contacts.readonly is enough for a read-only setup — plus contacts.other.readonly only 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
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.
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
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@latest
codex mcp list
claude mcp add \
--transport stdio --scope user google-contacts \
-- npx -y mcp-google-contacts@latest
claude mcp list
The 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.
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.
people/c..., contactGroups/..., otherContacts/...); tools address records by it, exactly as the API returns it.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.
| 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.
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.
Say "connect Google Contacts" and the assistant runs the flow with you:
setup_instructions prints the checklist: create or select a Google Cloud project, enable Google People API, configure the consent screen and create a Desktop app OAuth client.set_client stores it owner-only. The secret never goes through the conversation.start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.finish_login exchanges 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.
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.
Every variable is optional — with none of them the server connects from the chat.
| Variable | Required | Description |
|---|---|---|
GOOGLE_CONTACTS_CLIENT_ID | No* | OAuth client ID. |
GOOGLE_CONTACTS_CLIENT_SECRET | No* | OAuth client secret. |
GOOGLE_CONTACTS_REFRESH_TOKEN | No* | OAuth refresh token. |
GOOGLE_CONTACTS_ACCESS_TOKEN | No* | Short-lived alternative to the OAuth trio (~1 h). |
GOOGLE_CONTACTS_OAUTH_PORT | No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
GOOGLE_CONTACTS_API_BASE | No | Google People API base URL override. |
GOOGLE_CONTACTS_TIMEOUT_MS | No | Per-request timeout; default 60000 ms. |
GOOGLE_CONTACTS_MAX_RETRIES | No | Temporary-error retries; default 3. |
* 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.
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. Set ASKADS_TELEMETRY=0 to opt out.429 the server backs off and retries; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure.list_contacts supports 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.Found a bug or need a scenario? Create an issue or write in Telegram.
You made it to the end!