Google Contacts MCP Tools for AI Agents
Let an agent search contacts by name, email, or phone, look up your organization directory, and create contact records in Google Contacts.
Available Tools
6 tools available in this integration
GoogleContacts.CreateContact Create a new contact record in Google Contacts.
GoogleContacts.SearchContactsByEmail Search the user's contacts in Google Contacts by email address.
GoogleContacts.SearchContactsByName Search the user's contacts in Google Contacts by name.
GoogleContacts.SearchContactsByPhoneNumber Search the user's contacts in Google Contacts by phone number.
GoogleContacts.SearchDirectoryPeople Search the user's Google Workspace organization directory by name or email.
GoogleContacts.WhoAmI Get comprehensive user profile and Google Contacts environment information.
Why agent-optimized tools matter
Built for intent, not API schemas
Ask the agent to "find the contact for Jordan Lee and show me the work email before I call." Arcade helps it use the right Google Contacts tools without guessing whether to search by name, email, or phone.
Up to 100x fewer tokens
Google Contacts searches narrow the response to matching contact or directory records instead of loading an entire address book. The agent gets the fields needed to choose a person without filling the context window with unrelated entries.
Complete the workflow end to end
Search personal contacts, check the organization directory, confirm the person, create a contact, and return the saved record through one toolkit designed around the complete contact-management task.
Make actions predictable and controlled
Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.
Securing Google Contacts
The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.
This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.
Learn about Contextual Access PoliciesFor Google Contacts, you can implement some of these policies:
- Hide GoogleContacts.CreateContact from agents unless the roles your IDP marks as contact managers are active, so regular agents cannot add unreviewed people to users' address books.
- Require human approval before GoogleContacts.CreateContact runs, so an agent cannot create fraudulent or mistaken contact records.
- Strip phone numbers and postal addresses from GoogleContacts.SearchContactsByEmail results, so matching a person by email does not expose unrelated personal details.
- Redact personal phone numbers and home addresses from GoogleContacts.SearchDirectoryPeople results, so the agent receives directory identities without private contact data.
- Redact account identifiers, recovery contact details, and organization-specific environment identifiers from GoogleContacts.WhoAmI results before they reach the model.
How to use Google Contacts with your agent
Connect Google Contacts to an MCP client and give your agent access to the contact workflows it needs. Follow the walkthrough to configure authorization and run your first prompt.
Your questions, answered
A Google Contacts MCP server exposes contact and directory capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes Google, the agent can search contacts, look up directory people, inspect the connected profile, and create contacts.
Google Contacts does not provide the first-party MCP endpoint described here. Arcade provides the runtime around these actions, including per-user OAuth, approval workflows, response redaction, and access controls for agents and clients.
Arcade agents can create contacts, search personal contacts by name, email address, or phone number, search a Google Workspace directory by name or email, and retrieve the connected user's profile and Contacts environment information.
Read-only contact and directory searches require the relevant Google People API read scopes, while creating a contact requires write access to contacts. Grant the narrowest Google OAuth permissions that support your workflow.
Yes. Each user authorizes their own Google account through OAuth. Actions run under that user's authorization, so an agent can access only the contacts and directory information that user has approved.
Yes. Contextual Access policies can require human approval before a contact is created. The call proceeds only after the policy's conditions have been satisfied; read-only searches can also be governed by approval or hidden from an agent.
Arcade proxies Google Contacts API calls and does not persist your contact content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives them.
Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.
Arcade refreshes access while the user's Google authorization remains valid. If access is revoked, rotated, or can no longer be refreshed, calls stop until the user reconnects their Google account.
Calls are subject to Google People API quotas and any applicable Google account or Workspace limits. Contact searches and directory lookups do not remove those underlying Google limits.