CRM
Google Contacts MCP connector
The Google Contacts connector lets Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent search, look up, and tidy the contacts in a person's Google account, inside that person's own access, with every call recorded in an audit log.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
6 tools
How to connect
How to connect Google Contacts to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Google Contacts once
-
Open Connections, choose Add connection, and pick Google Contacts.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Google Contacts. Google Contacts's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Google Contacts to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Google Contacts to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Google Contacts to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Google Contacts to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Google Contacts through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Find the right person before a call
Ask for everyone at a customer account and get names, email addresses, phone numbers, and job titles from Google Contacts without opening a browser tab.
-
Support
Look up a customer's details fast
Pull a single contact's phone number, email, and company from Google Contacts while a ticket is open, so the reply goes to the right address the first time.
-
Office
Clean out duplicate and stale contacts
Search Google Contacts for duplicates or people who have left a supplier, review the list, and remove the entries that no longer belong.
-
Marketing
Spot people you email but never saved
Surface the other contacts in Google, the people you have corresponded with but never added, and decide who should join the next campaign list.
-
Recruiting
Pull together a shortlist of past candidates
Search Google Contacts for candidates by role or company and get a ready list of names and email addresses to reach out to again.
-
Executive assistants
Answer who knows whom across the team
Ask which saved contacts belong to a given organization and check whose Google account the connection is signed in as before sending an introduction.
Try asking
- “Find contacts in Google Contacts with no email address.”
- “Show contacts added this month and their organizations.”
- “List other contacts that are not saved contacts yet.”
AI tools
Google Contacts tools for your AI agents
6 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Contacts, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Google Contacts gets you
6 screens from the product, each doing one job for your Google Contacts account.
The agent
Ask about contacts, get answers back.
Plain language questions run against live Google Contacts records and return real names.
- contacts
- other contacts
- people
- email addresses
Ask Elaichi to work across your apps.
Find contacts in Google Contacts with no email address.
Show contacts added this month and their organizations.
List other contacts that are not saved contacts yet.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Google Contacts reaches every MCP client through one org endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
6 Google Contacts tools, no custom code.
Contacts, other contacts, people and userinfo methods are cataloged and ready to call.
- List all Google Contacts search contacts
- Get single Google Contacts search contact by ID
- Delete a Google Contacts search contact by ID
- List all Google Contacts other contacts
ElaichiToolsToolboxes
Every team gets its own toolbox.
Scope Google Contacts toolboxes to Sales, Support or Recruiting and keep the rest out.
- Sales
- Support
- Recruiting
- Marketing
ElaichiToolboxesShared connections
Teammates use the contacts, never the credential.
See who connected each Google Contacts account and which teams and members it reaches.
- Sales EMEA
- Sales AMER
- Support
- Marketing
ElaichiConnectionsAudit log
Every contact lookup has a name on it.
When, who, what happened, type and resource for each Google Contacts call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Fetch contacts, group them, draft a digest, approve it, then write back to Google Contacts.
Google Contacts digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contacts
Google Contacts
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Contacts
Queued
Collections and dashboards
Contact numbers arrive without being asked for.
Four metrics, 14 days of contacts created and a team breakdown, refreshed on schedule.
Google Contacts health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Other contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales AMER 27%
Support 21%
Marketing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Google Contacts to Claude?
Two steps. First, connect Google Contacts in Elaichi, which opens the normal Google sign-in screen where you choose your account and approve access, with no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you into Elaichi and Google Contacts is available in the conversation.
Does Google Contacts work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Contacts is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Google Contacts once and every client you use picks it up.
What can an AI agent actually do with my Google Contacts data?
Through Elaichi, an AI agent can search your Google Contacts by name, company, or email, open a single contact to read their phone number, address, and job title, and list the people you have emailed but never saved. It can also delete a contact you point it at and confirm which Google account it is signed in as. It cannot create or edit contacts through this connector.
Does connecting Google Contacts give the AI access to everyone's address book?
No. Access follows the person who signed in, so the AI sees only the Google Contacts that person can already see in their own Google account. Elaichi can narrow that access further, for example by hiding the option to delete contacts, but it can never widen it beyond what Google itself allows that person.
Can I stop an agent from deleting contacts in Google Contacts?
Yes. Restrictions in Elaichi work per action, so you can allow searching and reading Google Contacts while blocking deletion entirely. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a Google Contacts connection when someone leaves?
Offboarding that person in Elaichi ends their access to Google Contacts at once, in every client they had connected. If they shared a Google Contacts connection with a team, it keeps working for everyone else. Disconnecting Google Contacts once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Google Contacts in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.