Google Contacts

io.github.domdomeggPublished by GitHub account domdomeggv1.3.0Updated Oct 24, 2026

Allow AI systems to list, search, and manage contacts via Google Contacts.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that lets an assistant list, search, create, update and delete Google Contacts, including photos and contact groups.

What you can do
List and search contacts by name, email or phone, and look up coworkers in the organization directory; read full details for a single contact, including emails, phones, organizations, birthdays, addresses and custom fields; Create, update and permanently delete contacts, and set or remove contact photos; List, create, rename and delete contact groups and add or remove members.
When to use it
Useful when an assistant should look up someone's email or phone while drafting messages, capture new contacts from business cards or networking, search your personal network by company or city, or keep contact details current after someone changes jobs.
Requirements
Runs locally via npx (Node.js). Needs Google OAuth credentials: GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, with the People API enabled in a Google Cloud project and the redirect URI set to the local callback. MCP_TRANSPORT is required; the README runs it as an HTTP server on localhost:3000 by default (PORT configurable). GOOGLE_ACCESS_TOKEN is also declared as a required secret. Desktop only.
Before you install
It can create, update and permanently delete contacts, photos and contact groups, so mistakes are destructive. It handles Google OAuth secrets (GOOGLE_CLIENT_SECRET, GOOGLE_ACCESS_TOKEN) and acts as an OAuth proxy to Google, so the credentials grant access to your Google account's contacts. Contact data is sent to Google's People API.

Installation

In SourceWeft

  1. Open Google Contacts in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

google-contacts-mcp

MCP server for Google Contacts - list, search, and manage contacts.

Use Cases

Email lookup: "See the latest JIRA ticket that's come in. Can we email Sarah from the security team to get their input?" → finds Sarah's email and drafts the message.

Business card capture: After a networking event, snap photos of business cards → your assistant extracts the details and adds them as contacts with a note about where you met.

Find connections: "Who do I know at Google?" or "I'm visiting London next week - who should I catch up with?" → search your personal network.

Call reminder: "Remind me to call Mike at 3pm" → creates a calendar event with Mike's phone number attached so you can dial straight from the reminder.

Contact updates: You receive an out-of-office saying someone left their company with a new personal email → your assistant updates their contact automatically.

(These are just examples - any workflow that needs contact lookup or management can use this.)

Setup

1. Create Google OAuth credentials

  1. Go to Google Cloud Console
  2. Create a new project (or use existing)
  3. Enable the People API
  4. Go to APIs & Services → OAuth consent screen, set up consent screen
  5. Go to APIs & Services → Credentials → Create Credentials → OAuth client ID
  6. Choose Web application
  7. Add http://localhost:3000/callback to Authorized redirect URIs
  8. Note your Client ID and Client Secret

2. Run the server

bash
GOOGLE_CLIENT_ID='your-client-id' \GOOGLE_CLIENT_SECRET='your-client-secret' \MCP_TRANSPORT=http \npm start

The server runs on http://localhost:3000 by default. Change with PORT=3001.

3. Add to your MCP client

With the server running, follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

Architecture

This server acts as an OAuth proxy to Google:

mermaid
graph LR    A[MCP client] <--> B[google-contacts-mcp] <--> C[Google OAuth/API]
  1. Server advertises itself as an OAuth authorization server via /.well-known/oauth-authorization-server
  2. /register returns the Google OAuth client credentials
  3. /authorize redirects to Google, encoding the client's callback URL in state
  4. /callback receives the code from Google and forwards to the client's callback
  5. /token proxies token requests to Google, injecting client credentials
  6. /mcp handles MCP requests, using the bearer token to call People API

The server holds no tokens or state - it just proxies OAuth to Google.

Tools

ToolDescription
contacts_listList contacts with names, emails, phones, organizations, birthdays, events, URLs, addresses, nicknames, relations, IM usernames, genders, external IDs, client data, and custom fields
contacts_searchSearch contacts by name, email, or phone
directory_searchSearch organization directory for coworkers
contact_getGet detailed info for a single contact
contact_createCreate a new contact
contact_updateUpdate an existing contact
contact_deletePermanently delete a contact
contact_photo_updateSet or replace a contact's photo
contact_photo_deleteRemove a contact's photo
contact_groups_listList contact groups (labels)
contact_group_getGet a contact group, including its members
contact_group_createCreate a new contact group
contact_group_updateRename a contact group
contact_group_deletePermanently delete a contact group
contact_group_members_modifyAdd or remove contacts from a contact group

Contributing

Pull requests are welcomed on GitHub! To get started:

  1. Install Git and Node.js
  2. Clone the repository
  3. Install dependencies with npm install
  4. Run npm run test to run tests
  5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

  1. Use npm version <major | minor | patch> to bump the version
  2. Run git push --follow-tags to push with tags
  3. Wait for GitHub Actions to publish to the NPM registry.

Source: README.md at commit 80591d6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.