What is the key difference between Google Calendar MCP and Temporal Cortex MCP?

Google Calendar MCP belongs to the Workplace & Productivity category with local stdio execution, while Temporal Cortex MCP belongs to the Workplace & Productivity category with local stdio execution.

How do I install Google Calendar MCP or Temporal Cortex MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Google Calendar MCP and Temporal Cortex MCP free or paid?

Google Calendar MCP operates under a BYOK (Pay Provider Direct) model (OAuth 2.0). Temporal Cortex MCP operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Google Calendar MCP lists 3 tools with 2 views and 59 GitHub stars. Temporal Cortex MCP lists 18 tools with 3 views and 13 GitHub stars.

Can I use both Google Calendar MCP and Temporal Cortex MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Google Calendar MCP vs Temporal Cortex MCP

In-depth architectural comparison of the Google Calendar MCP and Temporal Cortex 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

Google Calendar MCP

Workplace & Productivity · Local stdio

Quality: 55/100 (Good) | Auth: OAuth 2.0

Temporal Cortex MCP

Workplace & Productivity · Local stdio

Quality: 65/100 (Great) | Auth: other

Verdict Summary: Choose Google Calendar MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Temporal Cortex 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 Google Calendar MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (BYOK (Pay Provider Direct)).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, TOKEN_ENCRYPTION_KEY, PORT.
Primary tools included: event, start, end.

Explore Google Calendar MCP Details

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.

Feature & Specification Comparison

Specification	Google Calendar MCP takumi0706 Workplace & Productivity	Temporal Cortex MCP temporal-cortex Workplace & Productivity
Summary	An MCP server to interface with the Google Calendar API. Based on TypeScript.	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.
Category & Scope

Tools & Capabilities Breakdown

Google Calendar MCP Tools (3)

event

Event details object containing:

start

Start time object with:

end

End time object (same format as start)

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

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).

Google Calendar MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "takumi0706-google-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@takumi0706/google-calendar-mcp@2.0.0"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "GOOGLE_REDIRECT_URI": "YOUR_GOOGLE_REDIRECT_URI_HERE",
        "TOKEN_ENCRYPTION_KEY": "YOUR_TOKEN_ENCRYPTION_KEY_HERE",
        "PORT": "YOUR_PORT_HERE"
      }
    }
  }
}

Temporal Cortex MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "temporal-cortex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "MICROSOFT_CLIENT_ID": "YOUR_MICROSOFT_CLIENT_ID_HERE",
        "TIMEZONE": "YOUR_TIMEZONE_HERE"
      }
    }
  }
}

Frequently Asked Questions

Google Calendar MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Temporal Cortex MCP belongs to Workplace & Productivity using local stdio subprocess. Select Google Calendar MCP when you need capabilities focused on workplace & productivity and Temporal Cortex MCP when you require tools for workplace & productivity.

More alternatives to Google Calendar MCP More alternatives to Temporal Cortex MCP Workplace & Productivity category hub