google-contacts-mcp
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
Go to Google Cloud Console
Create a new project (or use existing)
Enable the People API
Go to APIs & Services → OAuth consent screen, set up consent screen
Go to APIs & Services → Credentials → Create Credentials → OAuth client ID
Choose Web application
Add
http://localhost:3000/callbackto Authorized redirect URIsNote your Client ID and Client Secret
2. Run the server
GOOGLE_CLIENT_ID='your-client-id' \
GOOGLE_CLIENT_SECRET='your-client-secret' \
MCP_TRANSPORT=http \
npm startThe 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:
graph LR
A[MCP client] <--> B[google-contacts-mcp] <--> C[Google OAuth/API]Server advertises itself as an OAuth authorization server via
/.well-known/oauth-authorization-server/registerreturns the Google OAuth client credentials/authorizeredirects to Google, encoding the client's callback URL in state/callbackreceives the code from Google and forwards to the client's callback/tokenproxies token requests to Google, injecting client credentials/mcphandles MCP requests, using the bearer token to call People API
The server holds no tokens or state - it just proxies OAuth to Google.
Tools
Tool | Description |
| List contacts with names, emails, phones, organizations, birthdays, events, URLs, addresses, nicknames, relations, IM usernames, genders, external IDs, client data, and custom fields |
| Search contacts by name, email, or phone |
| Search organization directory for coworkers |
| Get detailed info for a single contact |
| Create a new contact |
| Update an existing contact |
| Permanently delete a contact |
| Set or replace a contact's photo |
| Remove a contact's photo |
| List contact groups (labels) |
| Get a contact group, including its members |
| Create a new contact group |
| Rename a contact group |
| Permanently delete a contact group |
| Add or remove contacts from a contact group |
Contributing
Pull requests are welcomed on GitHub! To get started:
Install Git and Node.js
Clone the repository
Install dependencies with
npm installRun
npm run testto run testsBuild with
npm run build
Releases
Versions follow the semantic versioning spec.
To release:
Use
npm version <major | minor | patch>to bump the versionRun
git push --follow-tagsto push with tagsWait for GitHub Actions to publish to the NPM registry.