Temporal Cortex MCP vs Google Workspace MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Temporal Cortex MCP vs Google Workspace MCP
In-depth architectural comparison of the Temporal Cortex MCP and Google Workspace MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Temporal Cortex MCP
Workplace & Productivity · Local stdio
Quality: 65/100 (Great) | Auth: other
Google Workspace MCP
Workplace & Productivity · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Temporal Cortex MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Google Workspace MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Temporal Cortex MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_ID, TIMEZONE.
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_REDIRECT_URI, WORKSPACE_MCP_LOG_LEVEL, WORKSPACE_MCP_PORT, WORKSPACE_MCP_HOST.
AI-native calendar middleware for scheduling, availability, and conflict-free booking across Google Calendar, Outlook, and CalDAV. 15 tools across 5 layers: temporal context, calendar operations, multi-calendar availability, open scheduling, and Two-Phase Commit booking. Deterministic datetime resolution and RRULE expansion powered by Truth Engine.
Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.
Category & Scope
Tools & Capabilities Breakdown
Temporal Cortex MCP Tools (18)
adjust_timestamp
Adjust a timestamp by adding or subtracting a duration. DST-aware: '+1d' preserves wall-clock time across daylight saving transitions.
book_slot
Book a calendar slot using Two-Phase Commit for safe, conflict-free booking.
check_availability
Check if a calendar time slot is available (not held by another booking).
compose_proposal
Compose a scheduling proposal message with proposed time slots. Formats times in the specified timezone for email, Slack, or SMS. Does NOT send the message — returns formatted text for the agent to send via its channel MCP (Gmail, Slack, etc.).
compute_duration
Compute the duration between two timestamps. Returns days, hours, minutes, seconds, and a human-readable string.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Temporal Cortex MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Google Workspace MCP belongs to Workplace & Productivity using local stdio subprocess. Select Temporal Cortex MCP when you need capabilities focused on workplace & productivity and Google Workspace MCP when you require tools for workplace & productivity.
Primary tools included: Full coverage of 12 major Google Workspace services with 120+ tools, OAuth 2.1 multi-user authentication with external auth passthrough support, Supports stdio, streamable HTTP, and SSE transports.
Expand a recurrence rule (RRULE) into concrete event instances.
find_free_slots
Find available free time slots in a calendar within a time window.
get_availability
Get unified availability across multiple calendars. Merges events from all specified calendars into a single busy/free view with privacy controls.
get_temporal_context
Get the current temporal context — time, timezone, calendar metadata. Call this first to orient yourself in time before making calendar queries.
list_calendars
List all connected calendars across providers. Returns calendar IDs, names, labels, and metadata. Call this first to discover what calendars are available before using other calendar tools.
list_events
List calendar events in a time range. Returns events in TOON or JSON format.
+6 more tools listed on main page
Google Workspace MCP Tools (6)
Full coverage of 12 major Google Workspace services with 120+ tools
OAuth 2.1 multi-user authentication with external auth passthrough support
Supports stdio, streamable HTTP, and SSE transports
Stateless deployment suitable for containerized environments
Includes CLI and code mode for developer tool integration