by rayanzaki
Integrate with Google Contacts to easily list, search, create, update, and delete contacts from personal and Google Work
Connects to your Google Contacts and Google Workspace directory to let you manage contacts directly through AI assistants. Requires Google API setup with OAuth credentials.
Google Contacts is a community-built MCP server published by rayanzaki that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with Google Contacts to easily list, search, create, update, and delete contacts from personal and Google Work It is categorized under productivity.
You can install Google Contacts in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Google Contacts is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
README content is unavailable from source data for this server.
Open GitHub repository →Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired Google Contacts into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Google Contacts is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend Google Contacts for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
According to our notes, Google Contacts benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Google Contacts reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Google Contacts against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend Google Contacts for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Google Contacts into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Google Contacts is the kind of server we cite when onboarding engineers to host + tool permissions.
Useful MCP listing: Google Contacts is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 73
Slack
MCP server for Slack — enables Claude to interact with Slack data and workflows.
★ —
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
