[ MCP SERVER SUMMARY ]
Google Calendar's remote MCP server lets AI agents list calendars, check availability, and create or update events with the user's Calendar permissions. Bifrost centralizes OAuth and applies tool policies so scheduling automation stays enterprise-safe.
| Property | Details |
|---|---|
| Company | |
| Connection type | HTTP |
| Authentication | OAuth 2.0 (Google Cloud client) |
| Package or endpoint | https://calendarmcp.googleapis.com/mcp/v1 |
| Capabilities | List calendars and events, Create update delete events, Suggest meeting times |
| Official documentation | Google Calendar MCP documentation |
[ HOW TO CONNECT ]
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Endpoint: https://calendarmcp.googleapis.com/mcp/v1.
• Enable calendar-json.googleapis.com and calendarmcp.googleapis.com.
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Google Calendar.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "google-calendar",
"connection_type": "http",
"connection_string": "https://calendarmcp.googleapis.com/mcp/v1",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Virtual keys, RBAC, and tool allowlists per team or agent.
Attribute MCP tool spend alongside LLM usage in one view.
Log every tool call with latency, server, and virtual key metadata.
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Google Calendar exposes list calendars and events, create update delete events, suggest meeting times to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
Google Calendar uses OAuth 2.0 (Google Cloud client). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Yes. After registering Google Calendar in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.
Connect AI assistants to files and folders in Google Drive through Google Workspace MCP.
Enable AI assistants to work with Google Chat spaces, messages, and collaboration workflows through Google Workspace MCP.