# 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. Source: https://elaichi.ai/connectors/googlecontacts/ ## Facts | | | | --- | --- | | Application | Google Contacts | | Category | CRM | | AI tools | 6 | | Authentication | Connects over OAuth | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Google Contacts is connected - 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. ## Connect Google Contacts in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Google Contacts. 2. Optionally set Share with, then press Connect. 3. Approve it in Google Contacts. Google Contacts's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Google Contacts tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Google Contacts to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Google Contacts to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Google Contacts tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Google Contacts through Elaichi ### Find the right person before a call Sales. 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. ### Look up a customer's details fast Support. 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. ### Clean out duplicate and stale contacts Office. Search Google Contacts for duplicates or people who have left a supplier, review the list, and remove the entries that no longer belong. ### Spot people you email but never saved Marketing. Surface the other contacts in Google, the people you have corresponded with but never added, and decide who should join the next campaign list. ### Pull together a shortlist of past candidates Recruiting. Search Google Contacts for candidates by role or company and get a ready list of names and email addresses to reach out to again. ### Answer who knows whom across the team Executive assistants. Ask which saved contacts belong to a given organization and check whose Google account the connection is signed in as before sending an introduction. ## 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 my team share one Google Contacts connection? Yes. One person connects Google Contacts in Elaichi and shares the connection with a team, and nobody else ever handles a password or token. Each teammate still signs into Elaichi as themselves, so the audit log records exactly who searched for or removed a contact. ### 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. ## All 6 Google Contacts tools Every tool below is callable through https://api.elaichi.ai/mcp once Google Contacts is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Google Contacts search contacts** (List). Get a list of contacts matching the query in Google Calendar. Requires query and readMask. Returns matched contacts with fields specified in readMask such as names, emailAddresses, phoneNumbers, and organizations. - **Get single Google Contacts search contact by ID** (Get). Get information about a specific contact by id in Google Calendar. Requires personFields parameter specifying which fields to return such as names, emailAddresses, phoneNumbers, and organizations. - **Delete a Google Contacts search contact by ID** (Delete). Delete a contact person by id in Google Calendar. The response is empty if successful. Non-contact data will not be deleted. Mutate requests must be sent sequentially to avoid latency and failures. - **List all Google Contacts other contacts** (List). Get a list of other contacts matching the query in Google Calendar. Requires query and readMask parameters. Returns matched contacts with fields emailAddresses, metadata, names, and phoneNumbers. - **List all Google Contacts userinfo** (List). Retrieves basic profile information about the authenticated user in Google Calendar. The response includes essential details such as the user's unique identifier (sub), full name (name), first name (given_name), last name (family_name), profile picture URL (picture), and email address (email). - **List all Google Contacts people** (List). List people from the Google directory via the People API. Returns a collection of people objects from the caller's domain directory.