Connect
Optimize
Secure
Google Contacts MCP Server
for AI Agents
Production-ready Google Contacts MCP server with extensible actions — plus built-in authentication, security, and optimized execution.
Google Contacts MCP Server
Built by 
StackOne
StackOne 
Coverage
16 Agent Actions
Create, read, update, and delete across Google Contacts — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your Google Contacts MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every Google Contacts tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.
Prompt Injection Defense →
Performance
Max Agent Context. Min Cost.
Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Google Contacts call.
Tools Discovery →What is the Google Contacts MCP Server?
A Google Contacts MCP server lets AI agents read and write Google Contacts data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Google Contacts MCP server ships with pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Cursor, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.
All Google Contacts MCP Tools and Actions
Every action from Google Contacts's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Contacts
- Create Contact
Create a new contact
- List Contacts
List the authenticated user's contacts
- Get Contact
Get a single contact by resource name
- Search Contacts
Search the user's contacts
- Update Contact
Update an existing contact
- Batch Get Contacts
Get multiple contacts by resource names
- Delete Contact
Delete a contact
Contact Groups
- Create Contact Group
Create a new contact group
- List Contact Groups
List all contact groups owned by the authenticated user
- Get Contact Group
Get a specific contact group by resource name
- Update Contact Group
Update an existing contact group
- Delete Contact Group
Delete an existing contact group
Modify Contact Group Members
- Modify Contact Group Members
Add or remove members from a contact group
Other Contacts
- List Other Contacts
List other contacts (automatically saved contacts)
- Search Other Contacts
Search other contacts by query
Other Contact To My Contacts
- Copy Other Contact To My Contacts
Copy an other contact to the user's contacts
Set Up Your Google Contacts MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to Google Contacts in under 10 lines of code.
MCP Clients
Agent Frameworks
JSON{
"mcpServers": {
"stackone": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://api.stackone.com/mcp?x-account-id=<account_id>",
"--header",
"Authorization: Basic <YOUR_BASE64_TOKEN>"
]
}
}
}Google Contacts MCP Server Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
Google Contacts MCP Server FAQ
Google Contacts MCP server vs direct API integration — what's the difference?
A Google Contacts MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Google Contacts. A Google Contacts MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Google Contacts at runtime. StackOne provides both.
How does Google Contacts authentication work for AI agents?
Google Contacts authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Google Contacts account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are Google Contacts MCP tools vulnerable to prompt injection?
Yes — Google Contacts MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Google Contacts agent and how do I avoid it?
Context bloat happens when Google Contacts tool schemas and API responses eat your Google Contacts agent's memory, preventing it from reasoning effectively. A single Google Contacts query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Google Contacts agent can access?
Yes — you can limit which actions your Google Contacts agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Google Contacts MCP server?
Yes — you can create custom agent actions for your Google Contacts MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Google Contacts's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Google Contacts MCP server?
Skip a Google Contacts MCP server if your integration is purely software-to-software — direct Google Contacts API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Google Contacts actions at runtime.
What AI frameworks and AI clients does the StackOne Google Contacts MCP server support?
The StackOne Google Contacts MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.
Put your AI agents to work
All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.