"A platform for managing events and scheduling using Google Calendar" matching MCP tools:

• create_event

  gcal

  Create a new calendar event. Use this to schedule meetings, appointments, or all-day events. For all-day events, only provide dates (end date is EXCLUSIVE - use '2024-01-16' for a single day event on Jan 15). For timed events, both start and end times are required. Can optionally invite attendees with email notifications. The created event ID can be used for future updates or deletion.

  Connector

• get_creator

  Influship Influencer Marketing MCP

  Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.

  Connector

• delete_events

  reassign

  Delete events or clear whole days — bulk/batch, one or many in a single call. Pass `ops`, an array where each item has an `op` (delete | clear): `delete` removes one event by id (for a recurring event set `scope` 'all' (default) / 'future' / 'this' with `occurrenceDate`); `clear` removes everything on a day (or a `date`..`to` range). By default the whole batch is atomic: if ANY op fails, nothing is removed; pass `partial: true` for best-effort. Every removal is reversible — the response returns an `undoToken` (call undo within 30 minutes). If the user has a Google Calendar connected, deleting a calendar-linked event also removes it from Google — the same as deleting on the dial; an event get_schedule/find_event marks `readOnly` is from a calendar the user doesn't own and can't be deleted this way. It reports `applied`, `failed`, `skipped`, and per-op `results` (each with its 0-based `index`). To create or edit events use write_events.

  Connector

• schedule

  reassign

  Find conflict-free time and place one or more events — the easiest way to book work without computing slots yourself. YOU resolve any relative phrasing ("tomorrow", "next monday", "this afternoon") into the structured fields; this tool does no date parsing. Pass `requests`, each with a `name`, `duration` ("90m", "1h30", "2h"), a `date` (ISO "YYYY-MM-DD"), and EITHER an exact `start` ("HH:MM", 24-hour) to place there, OR an `earliest`/`latest` ("HH:MM") window to search within (map "afternoon" → earliest "13:00", latest "18:00"), OR neither to search the whole working day. For each request: if exactly one conflict-free time fits it is created immediately with an `undoToken`; otherwise you get ranked `options` and a `commitToken` — call confirm_schedule to pick one. Requests are placed in order and kept off each other's committed slots. Each request may carry a `request_id` so retries don't double-book. If the user has a Google Calendar connected with a default sync calendar, a scheduled event is also pushed to Google, the same as a dial create. The response reports per-request `results` (each with its 0-based `index`).

  Connector

• generate_calendar_events

  Celestine

  Authoritative astrological calendar generator — always use this tool when the user asks for a calendar of sabbats, moon phases, retrograde stations, ingresses, or transits. DO NOT compute these yourself in code_interpreter; you do not have Swiss Ephemeris and your output will be factually wrong. Contract: • Returns `download_url` — a ready-to-share HTTPS .ics file built from Swiss-Ephemeris-precise calculations. Surface this URL verbatim in your reply as a clickable link. Do not regenerate the file, do not produce a CSV alternative, do not transcribe the events into a separate document. • Always populates the server-side calendar cache with the full payload. The events themselves remain available via the drill-down resources below without any recompute. Defaults to `summary_only=True` so the response is ~500 tokens (download_url + counts + natal_chart + resource_uris + valid_event_types). Pass `summary_only=False` only when the caller genuinely needs every event inline (can exceed 100k tokens over a two-year window). Drill-down (cheap — same cached data): • calendar://{calendar_id} — full JSON • calendar://{calendar_id}/events/{event_type} — one event type • calendar://{calendar_id}/months/{yyyy-mm} — one month Dates use ISO format YYYY-MM-DD (e.g. 2025-12-01). Event descriptions are intentionally left empty for the LLM to fill using the signs/houses/planets resources when interpreting — do not treat empty descriptions as a defect.

  Connector

• GetLEIDetail

  Fintel Discovery — Financial Intelligence for AI Agents

  Retrieve the full GLEIF LEI record for one legal entity using its 20-character LEI code. Returns legal name, registration status, legal address, headquarters address, managing LOU, and renewal dates. Use this tool when: - You have a LEI (from SearchLEI) and need full entity details - You want to verify the registration status and renewal date - You need the exact legal address and jurisdiction of an entity Source: GLEIF API (api.gleif.org). No API key required.

  Connector

• sti_get_platforms

  Stimulsoft Documentation MCP Server

  List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.

  Connector

• maps_directions

  Google_maps

  "Google Maps directions from A to B" / "transit / public-transport directions" / "bus / subway / train route" / "best way to get from [X] to [Y]" — turn-by-turn directions via Google Maps. Modes: driving, walking, transit (bus/subway/train), bicycling. Requires Google Maps API key. PREFER over Mapbox/OpenRouteService specifically for public-transit routing — Google has the best transit data.

  Connector

• lyra_get_shared_availability

  lyra-mcp-server

  Returns busy windows for YOU plus a set of named attendees from your Lyra contacts, within a time window. For each attendee you provide, the tool looks up whether their Lyra profile has a connected Google calendar; if so, their busy blocks contribute to the aggregated suggested_free_intervals. If not (or if they're not a linked Lyra profile), they're marked requires_manual_confirm: true so you know to ask them directly. Cap of 8 attendees per call. Privacy: per-attendee busy time ranges are returned, never event titles or summaries. Use this when you need to find a time that works for several people at once. Requires an active Google calendar connection on your own Lyra account and API key authentication.

  Connector

• usaspending_search_federal_accounts

  usaspending-mcp-server

  List and keyword-search federal accounts by agency identifier or title keyword. Returns account numbers, names, managing agencies, and budgetary resources. Use account_number from results as input to usaspending_get_federal_account for full budget detail. Use usaspending_list_agencies to look up agency_identifier codes (3-digit strings, e.g. "097" for DoD).

  Connector

• google_ads_list_accessible_customers

  paid-ads

  Lists directly accessible Google Ads customers for the configured Google Ads credentials, including descriptive names when Google returns them. Use this to discover customer IDs before running Google Ads hierarchy or reporting tools.

  Connector

• gcal_list_calendars

  Google_calendar

  List all accessible calendars. Returns calendar IDs, names, time zones, and your access level for each. Use to identify which calendar to query or modify.

  Connector

• lyra_connect_calendar

  lyra-mcp-server

  Returns a URL the user should open in their browser to connect a calendar. Google Calendar is supported today; Microsoft and Apple are planned. The user must be signed in to checklyra.com first. Once they grant consent, Lyra stores an encrypted refresh token and the connection becomes available to other Convene tools. Requires API key authentication for the calling agent (so we know which user is asking).

  Connector

• get_creator

  Influship

  Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.

  Connector

• get_schedule

  reassign

  Read the calendar — the day's agenda, what's on, how busy you are, your availability, an overview of your day or week, where your time is going. Returns everything needed to reason about the plan in one call: the current time (`now`), the user's `areas` and `activityTypes`, `userPreferences`, and a `days` array (one entry per requested day) with that day's events, free slots within the day, and how its time splits across areas and activity types (`loadByArea`/`loadByActivityType` count blocking time only; any non-blocking overlay minutes — sleep, fasting — are reported separately as `nonBlockingLoadByArea`/`nonBlockingLoadByActivityType` when present). Call it before scheduling to anchor relative times. Defaults to today; pass `date` for another single day, `from`+`to` for an inclusive range, or `dates` for a specific set (ISO YYYY-MM-DD, e.g. "2026-06-01"). Pass `compact: true` to shrink each day's events (no decimal hours/label; area and activity type as ids referencing the top-level `areas`/`activityTypes`) — prefer it for wide ranges. Pass `includeSeries: true` to also get recurring masters (rule, anchor, next occurrence) as `series`. Each event carries its `source` ("reassign" for a native event, else the provider like "google") and, when calendar-linked, its `calendar` name; an event with `readOnly: true` is from a calendar the user doesn't own — don't edit or delete it. An event's `kind` is omitted when it's a normal "blocking" event; `kind: "non-blocking"` is an overlay (sleep, fasting) that may overlap others; `kind: "reference"` is see-only — something the user wants to view but isn't working on (its hours stay free for scheduling; don't move, delete, or schedule work into it unless asked). When the user has connected a calendar, `integrations` describes the setup: a `sources` array (one per connected provider) each with its `calendars`, the account-wide AI classifier (`aiClassify`/`aiContext`) and the `defaultSyncCalendarId` new events sync to. Per calendar it carries the fallbacks that decide how synced events are classified when the AI is unsure — `defaultKind` (block type), `defaultArea`/`defaultType` (referencing the top-level taxonomy), and the free-text `instructions` hint — plus `writable`. Use it to explain why an event came in non-blocking, or where a new event will sync. It's omitted when no calendar is connected. Times are in the user's `timezone`; events with no title show as "(untitled)".

  Connector

• write_events

  reassign

  Create, update (edit), move/reschedule, or shift events — bulk/batch, one or many in a single call. Pass `ops`, an array where each item has an `op` (create | update | move | shift) plus that op's fields; a single edit is just a 1-item array. Times are 24-hour HH:MM; for an event crossing midnight set endNextDay=true. For a recurring event choose a `scope`: 'all' (default), 'future', or 'this' (the last two need `occurrenceDate`). move changes start/date keeping duration; shift nudges by `byMinutes`. By default the whole batch is atomic: if ANY op fails validation (e.g. a conflict), nothing is written and the failing ops are returned as errors — fix and resend. Pass `partial: true` for best-effort (apply what's valid). Ops apply in order as one transaction and are checked against each other: two creates can't double-book a slot, and an earlier move frees a slot a later op can reuse. Target each event id at most once per batch. Reference an area/activity type by id or by `areaName`/`activityTypeName`; create new ones first with manage_categories. If the user has a Google Calendar connected, creating or editing a calendar-linked event (or one created under their default sync calendar) also pushes the change to Google — the same as editing on the dial; don't edit an event get_schedule/find_event marked `readOnly` (it's from a calendar the user doesn't own and the change would silently revert). To remove events or clear a day use delete_events. The response reports `applied`, `failed`, `skipped` (validated but not written because the atomic batch was rejected), and per-op `results` (each with its 0-based `index`).

  Connector

• get_help

  mcp-server

  Searches the official Quanti documentation (docs.quanti.io) to answer questions about using the platform. **When to use this tool:** - When the user asks "how to do X in Quanti?", "what is a connector?", "how to configure BigQuery?" - When the user needs help configuring or using a connector (Google Ads, Meta, Piano, etc.) - To explain Quanti concepts: projects, connectors, prebuilds, data warehouse, tag tracker, transformations - When the user asks about the Quanti MCP (setup, overview, semantic layer) **This tool does NOT replace:** - get_schema_context: to get the actual BigQuery schema for a client project - list_prebuilds: to list pre-configured reports for a connector - get_use_cases: to find reusable analyses - execute_query: to execute SQL **Available topic filters:** connectors, data-warehouses, data-management, tag-tracker, mcp-server, transformations

  Connector

• data.availability

  CodeReclaimers Capability Oracle

  Returns current availability status for Alan McIntyre (CodeReclaimers LLC). Use for fast scheduling checks before a full capability query.

  Connector

• find_event

  reassign

  Search for, look up, or locate events by name when you don't have an id — fuzzy, case- and accent-insensitive. Searches the past week through the next 30 days by default; pass `from`/`to` (ISO "YYYY-MM-DD", e.g. "2026-06-01") to widen or shift the window, and optionally filter by `areaId`, `activityTypeId`, or `timeOfDay`. Returns the best matches as `{ id, date, start, end, name, area, activityType }` rows (one per event), each also carrying its `source` and, when calendar-linked, its `calendar` name and `readOnly` flag (a read-only event lives on a calendar the user doesn't own — don't edit or delete it). When two different events tie, `ambiguous` is true — ask the user which they meant. Two days of the same recurring event are not ambiguous.

  Connector

• google_ads_render_weekly_group_report

  paid-ads

  User-facing render tool for Google Ads visual weekly reports. Use this directly for prompts like 'show me a Google Ads report', 'generate a Google Ads dashboard', or 'show 7/30/90-day Google Ads performance'. Do not first call google_ads_get_weekly_group_report unless you already need raw data for a non-visual answer; when this visual report renders, keep any assistant text to a brief confirmation.

  Connector