Strider Google Calendar

Manage Google Calendar via Strider Labs MCP connector. Create, update, and delete events. Search availability, set reminders, and handle recurring meetings....

Security Scan

The skill's requirements and runtime instructions are internally consistent with a Google Calendar connector (it needs npx and an npm package and uses OAuth), but it relies on fetching/running a package from npm at runtime and omits details about token storage and exact OAuth scopes — verify those before trusting it with real accounts.

Purpose & Capability

Name/description match the actual instructions: the SKILL.md describes a Google Calendar MCP connector, lists calendar-related tools, and directs the agent to run an npm package via npx. Required binary (npx) is coherent with the claimed purpose.

Instruction Scope

Instructions stay within calendar management (create/list/update/delete, availability). They describe an OAuth flow (open authorization, grant access, token storage) which is expected. The SKILL.md does not ask the agent to read unrelated files or environment variables. It does not specify where tokens are stored or the exact OAuth scopes requested.

Install Mechanism

There is no built-in install spec; the skill expects runtime execution of an npm package via npx (npm install suggestion included). Fetching and running @striderlabs/mcp-gcal from the npm registry at runtime is normal for an MCP connector but is a higher-risk install pattern than instruction-only code because the package code will be downloaded and executed. Recommend verifying the package source and pinning versions if possible.

Credentials

No environment variables or unrelated credentials are requested, which is proportional. OAuth-based access is described (no API key required). A minor note: SKILL.md states tokens are stored encrypted per-user but gives no detail on storage location or key management.

Persistence & Privilege

always is false and the skill does not request persistent system-level privileges or modify other skills. Autonomous invocation is allowed (platform default) and appropriate for an assistant connector.

Assessment

This skill appears to do what it claims (a Google Calendar connector) and requires npx to run an npm package. Before installing or granting access: 1) Verify the npm package (@striderlabs/mcp-gcal) and its maintainer (check npm page and linked repository) to ensure the code is trustworthy and inspect recent release history. 2) Confirm the exact OAuth scopes requested during authorization and only grant the minimum needed (calendar read/write as appropriate). 3) Ask or verify where and how tokens are stored and encrypted on your platform. 4) Prefer pinning to a specific package version (avoid running unpinned npx commands in production) or run the package in a least-privileged/test account first. 5) If you have doubts about Strider Labs' identity or the package source, do not authorize with your primary calendar account.

Strider Google Calendar Connector

MCP connector for Google Calendar management. Part of the Strider Labs action execution layer for AI agents.

Installation

npm install @striderlabs/mcp-gcal

MCP Configuration

Add to your MCP client configuration (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "gcal": {
      "command": "npx",
      "args": ["-y", "@striderlabs/mcp-gcal"]
    }
  }
}

Available Tools

gcal.create_event

Create a new calendar event.

Input Schema:

{
  "title": "string",
  "start_time": "string (ISO 8601)",
  "end_time": "string (ISO 8601)",
  "description": "string (optional)",
  "location": "string (optional)",
  "attendees": ["[e-mail]", "[e-mail]"],
  "reminders": [{"method": "email", "minutes": 30}]
}

Output:

{
  "event_id": "abc123xyz",
  "html_link": "https://calendar.google.com/event?eid=...",
  "status": "confirmed"
}

gcal.get_events

List events within a date range.

Input Schema:

{
  "start_date": "string (YYYY-MM-DD)",
  "end_date": "string (YYYY-MM-DD)",
  "calendar_id": "string (optional, defaults to primary)"
}

gcal.find_availability

Find free time slots for scheduling.

Input Schema:

{
  "date": "string (YYYY-MM-DD)",
  "duration_minutes": "number",
  "start_hour": "number (0-23, optional)",
  "end_hour": "number (0-23, optional)"
}

gcal.update_event

Modify an existing event.

Input Schema:

{
  "event_id": "string",
  "title": "string (optional)",
  "start_time": "string (optional)",
  "end_time": "string (optional)",
  "location": "string (optional)"
}

gcal.delete_event

Remove an event from calendar.

Input Schema:

{
  "event_id": "string",
  "send_notifications": "boolean (optional)"
}

gcal.list_calendars

Get all calendars accessible to the user.

Authentication

Uses Google OAuth 2.0:

1. First use opens Google authorization
2. User grants calendar access
3. Tokens stored encrypted per-user
4. Automatic refresh when tokens expire

No API key required — connector manages OAuth flow.

Usage Examples

Schedule a meeting:

Schedule a team standup tomorrow at 9am for 30 minutes

Find availability:

Find a free hour next Tuesday for a client call

Check schedule:

What meetings do I have this week?

Reschedule:

Move my 3pm meeting to 4pm

Error Handling

Code	Meaning	Action
AUTH_EXPIRED	Google session expired	Re-authenticate
CALENDAR_NOT_FOUND	Invalid calendar ID	Check calendar list
TIME_CONFLICT	Overlapping event	Find different time
RATE_LIMITED	Too many requests	Retry after delay

Use Cases

• Meeting scheduling: create and manage calendar events
• Availability check: find free time slots for booking
• Event reminders: set up notifications before events
• Recurring events: schedule weekly/monthly meetings
• Shared calendars: manage team calendars

Links

• npm: https://npmjs.com/package/@striderlabs/mcp-gcal
• Strider Labs: https://striderlabs.ai
• Google Calendar API: https://developers.google.com/calendar