Skip to main content
Glama
309,877 tools. Last updated 2026-07-28 07:59

"Using Google Calendar for scheduling and organization" matching MCP tools:

  • List servers in an organization. Call forge_list_organizations first to get the organization id. Forge v2: GET /orgs/{organization}/servers.
    Connector
  • Retrieve the X (formerly Twitter) handle for a given person, organization, sports team, government entity, or descriptive phrase using AI-powered lookup. Returns the handle with a confidence score. Cost: $0.05 USDC via x402.
    Connector
  • Schedule multiple social media posts at once (up to 50 posts per batch). More efficient than scheduling posts individually.
    Connector
  • Create a new event in Google Calendar. Specify the title, start time, end time, and optionally invite attendees. Use ISO 8601 format for dates (e.g., 2024-12-15T14:00:00).
    Connector
  • Update an existing event in Google Calendar. Can modify title, time, location, description, and attendees. Only specified fields will be updated.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Check when you have free time in Google Calendar. Shows busy periods and free slots in a given time range. Useful for finding meeting times or checking schedule conflicts.
    Connector
  • Compare product prices across e-commerce platforms using Google Shopping and direct URL monitoring. Args: product_name: Product name to search product_urls: Direct product page URLs to check max_results: Max results (default 20)
    Connector
  • Book a 30-minute strategy session with TESSA on Kevin Callen's calendar. Finds an open slot in the requested window (or the next 5 business days), creates a Google Calendar event with a Google Meet link, and emails the prospect the invite. If no slot is available, captures the lead and Kevin follows up manually. TESSA-only tool — directory firms use request_introduction instead. requested_window accepts ISO 8601 ranges ('2026-04-30T13:00/2026-04-30T17:00'), single dates ('2026-04-30'), or English ('tomorrow', 'next week').
    Connector
  • Cancel a scheduled booking (call/meeting) and return the result — the invitee is notified per the scheduling settings. A write. Resolve booking_id via list_bookings first; never guess it. To move it instead of cancelling, use reschedule_booking.
    Connector
  • Sprints — name, goal, state, and window, newest first. Read-only; returns the matching sprints, empty when none exist. See the delivery cadence (active + recent), and resolve a sprint_id here before scheduling a task via create_task / update_task. Optional state filter (e.g. 'active').
    Connector
  • Upcoming confirmed bookings on the org's scheduling. Read-only; returns the bookings, empty when none are scheduled. Pass include='all' for full history.
    Connector
  • Get the name, organization, country, and description for an Autonomous System number. Lightweight version of as_whois.
    Connector
  • AUTH REQUIRED; WRITES A NEW SPALA ORGANIZATION FOR THE SIGNED-IN ACCOUNT. Creates an additional company or workspace organization using the supplied name.
    Connector
  • AUTH REQUIRED; READ-ONLY. Lists projects accessible to the authenticated Spala user in one organization. Accepts an organization id when multiple organizations are available and automatically scopes a sole organization.
    Connector
  • AUTH REQUIRED; WRITES TO THE SPALA CONTROL PLANE. Creates a real Spala project with the supplied project name in an accessible organization. Accepts an organization id when multiple organizations are available and automatically scopes a sole organization. This operation is not idempotent.
    Connector
  • Returns all contests currently open for entry. Typically 1–3 active (one per track). Low entry count = better odds. Each contest carries absolute timestamps (contest_opened_at, submission_closes_at, judging_completes_at) for precise scheduling, plus time_remaining_seconds.
    Connector