Google Contacts MCP connector
The Google Contacts connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects over OAuth
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Find contacts in Google Contacts with no email address.
Working in Google Contacts with Elaichi
-
List all Google Contacts search contacts
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Google Contacts to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Google Contacts MCP connector for 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.
Google Contacts MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Google Contacts MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Google Contacts MCP connector for 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.
Google Contacts MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Google Contacts through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Google Contacts is logged.
-
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.”
What connecting Google Contacts gets you
6 screens from Elaichi, each doing one job for your Google Contacts account.
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, Cursor or Microsoft Copilot
The agent
Ask about contacts, get answers back.
Plain language questions run against live Google Contacts records and return real names.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Google Contacts reaches every MCP client through one org endpoint, no SDK, no shared key.
ElaichiToolsTool catalog
6 Google Contacts tools, no custom code.
Contacts, other contacts, people and userinfo methods are cataloged and ready to call.
ElaichiToolboxesToolboxes
Every team gets its own toolbox.
Scope Google Contacts toolboxes to Sales, Support or Recruiting and keep the rest out.
ElaichiConnectionsShared connections
Teammates use the contacts, never the credential.
See who connected each Google Contacts account and which teams and members it reaches.
ElaichiAudit logAudit log
Every contact lookup has a name on it.
When, who, what happened, type and resource for each Google Contacts call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Google Contacts digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Google Contacts
Queued
Automations
A schedule fires, a digest ships.
Fetch contacts, group them, draft a digest, approve it, then write back to Google Contacts.
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%
Collections and dashboards
Contact numbers arrive without being asked for.
Four metrics, 14 days of contacts created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Google Contacts
All three can connect Google Contacts to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Google Contacts tools | Allow or restrict single Google Contacts tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Google Contacts call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting 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 restricting deletion entirely. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client at the same time.
Does the Google Contacts MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Google Contacts is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Google Contacts?
Yes. Both let Claude, ChatGPT or Cursor use Google Contacts. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Contacts call.
How is Elaichi different from Composio for Google Contacts?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Contacts: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Google Contacts in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot