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

Google Drive 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 Drive 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 Drive and Temporal Cortex MCP free or paid?

Google Drive operates under a Free / Open Source model (No auth required). Temporal Cortex MCP operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Google Drive lists 6 tools with 1 views and 0 GitHub stars. Temporal Cortex MCP lists 18 tools with 3 views and 13 GitHub stars.

Can I use both Google Drive 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 Drive vs Temporal Cortex MCP

In-depth architectural comparison of the Google Drive 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 Drive

Workplace & Productivity · Local stdio

Quality: 41/100 (Fair) | Auth: No auth required

Temporal Cortex MCP

Workplace & Productivity · Local stdio

Quality: 63/100 (Good) | Auth: other

Verdict Summary: Choose Google Drive 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 Drive when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, GOOGLE_SERVICE_ACCOUNT_KEY_PATH, GOOGLE_IMPERSONATE_USER, GOOGLE_DRIVE_ALLOW_WRITE, MCP_TRANSPORT, MCP_HTTP_TOKEN.
Primary tools included: Formula-aware Sheets editing, Full Slides editing, Shared-drive permission and activity audits.

Explore Google Drive 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: .

Feature & Specification Comparison

Specification	Google Drive Workplace & Productivity	Temporal Cortex MCP temporal-cortex Workplace & Productivity
Summary	Google Drive + Workspace MCP — Docs, Sheets, Slides, Shared Drives, Labels, Approvals, DWD	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 Drive Tools (6)

Formula-aware Sheets editing

Full Slides editing

Shared-drive permission and activity audits

OAuth2, service-account, and ADC authentication

Document and spreadsheet aggregation tools

Configurable tool categories and HTTP transport

Temporal Cortex MCP Tools (18)

adjust_timestamp

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 Drive Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "google-drive-5": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/google-drive-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "GOOGLE_REFRESH_TOKEN": "YOUR_GOOGLE_REFRESH_TOKEN_HERE",
        "GOOGLE_SERVICE_ACCOUNT_KEY_PATH": "YOUR_GOOGLE_SERVICE_ACCOUNT_KEY_PATH_HERE",
        "GOOGLE_IMPERSONATE_USER": "YOUR_GOOGLE_IMPERSONATE_USER_HERE",
        "GOOGLE_DRIVE_ALLOW_WRITE": "YOUR_GOOGLE_DRIVE_ALLOW_WRITE_HERE",
        "MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
        "MCP_HTTP_TOKEN": "YOUR_MCP_HTTP_TOKEN_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 Drive 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 Drive when you need capabilities focused on workplace & productivity and Temporal Cortex MCP when you require tools for workplace & productivity.

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