Date arithmetic against a real calendar. ops: add_business_days, diff, tz_convert, is_us_federal_holiday. Holiday data is United States federal only and every response says so.
ConnectorNo auth
726,971 tools. Updated 2026-10-31 01:38
"calendar" matching MCP tools:
- Chinese calendar for a date: lunar date (with leap month), zodiac, day officer 建除, yellow/black path, six-day cycle — computed on Beijing timeConnectorNo auth
- Upcoming US economic release dates (FRED calendar, live-fetch)ConnectorNo auth
- Upcoming US economic release dates (FRED calendar, live-fetch)ConnectorNo auth
- Sort corporate dates into what is still ahead and what has already passed. ★ TWO DATES, NOT ONE. What is "upcoming" is decided by the date the event HAPPENS; `as_of` filters on the date it was ANNOUNCED. An ex-dividend declared on 2026-08-01 for 2026-09-15 is both already known and still ahead on 2026-08-10. Collapsing the two fields either hides every future date or reports last month's ex-dividend as though it were coming. ★ ELAPSED DATES ARE SEPARATED, NOT DISCARDED. They come back under `past` — the previous ex-dividend is useful context for a question about the next one — but they can never appear under `upcoming`. ★ NOT `search_filings` AND NOT `query_dataset`. Those retrieve disclosures and rows; this one only arranges dated corporate events on a timeline relative to now. ⚠️ A scheduled date is a schedule, not a promise; companies move them. Args: rows (dated events), today (YYYY-MM-DD), optional as_of.ConnectorNo auth
- Upcoming scheduled catalysts for the next N days: US macro prints (CPI, PPI, jobs, PCE, GDP, retail, JOLTS) with ET times, FOMC decisions and minutes, Treasury auctions and earnings dates seen in the feed, each with the assets it usually moves. Use it to avoid holding through a print or to schedule polling. $0.002/call. Use for upcoming scheduled macro/earnings catalysts; for Treasury auction details use treasury_auctions.ConnectorNo auth
Matching MCP Servers
- AlicenseAqualityAmaintenanceThis project implements a Python-based MCP (Model Context Protocol) server that acts as an interface between Large Language Models (LLMs) and the Google Calendar API. It enables LLMs to perform calendar operations via natural language requests.2345 PyPI26AGPL 3.0
- AlicenseAqualityDmaintenanceExposes Apple Calendar data through an EventKit helper app. Enables reading, creating, updating, and deleting calendar events on macOS.714 npmMIT
Matching MCP Connectors
- Multi CalendarOAuth
Outlook.com, Microsoft 365, Google calendars: free time, events, invitations, booking pages, polls.
The Boston Calendar MCP.
- Upcoming scheduled catalysts for the next N days: US macro prints (CPI, PPI, jobs, PCE, GDP, retail, JOLTS) with ET times, FOMC decisions and minutes, Treasury auctions and earnings dates seen in the feed, each with the assets it usually moves. Use it to avoid holding through a print or to schedule polling. $0.002/call. Use for upcoming scheduled macro/earnings catalysts; for Treasury auction details use treasury_auctions.ConnectorNo auth
- Public holidays for a country between two dates, or whether a date is a business day and the date N business days later/earlier. Countries: GT SV HN NI CR PA BZ DO.ConnectorAPI key
- SMB: 14-day content calendar (posts+hashtags+times). input=brand, red=optional. [x402: 4.0 USDC on Base, pay-per-use]ConnectorNo auth
- Plan a 30-day content calendar: daily themes, post types, and a posting schedule. Use for planning a month of content. For the overall strategy behind it, use generate-marketing-strategy. For the posts themselves, use generate-linkedin-post or repurpose-long-form. Pay-per-call: $0.06 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.ConnectorNo auth
- WORKFLOW: 30-day multi-network content calendar. input=brand. B2B: agencies plan a month of content in one call. [x402: 20.0 USDC on Base, pay-per-use]ConnectorNo auth
- Add ELC Conference 2027 (22 April 2027, Prague) to the user's calendar: a Google Calendar link and an .ics entry built from the announced date. Venue to be announced.ConnectorNo auth
- Takes a phase and returns up to 50 Indian IPOs in it (default allotment-this-week): upcoming, open, closed, allotted, listed, or allotment-this-week (default, allotment dates from 2 days ago to 7 days ahead). Up to 50 rows, newest first, with dates, price, lot size and the page that checks allotment. Example input: {"phase":"allotment-this-week"}ConnectorNo auth
- Calendar Weeks: Returns the ISO week count (52 or 53) and leap-year flag for a given year 🆓 5 free trial calls per signed walletConnectorNo auth
- Calendar Weeks: Returns the ISO week count (52 or 53) and leap-year flag for a given year 🆓 5 free trial calls per signed walletConnectorNo auth
- Turn a custody or parenting-time rotation (week on/week off, 2-2-3, 2-2-5-5, 5-2-2-5, 3-4-4-3, alternate weekends, 4-3, or a custom cycle) into a dated calendar: which parent has the kids each night, the exchange days, each parent's overnight count and percentage for the year, and the longest stretch apart. Returns a calendar file (.ics) and a subscribe link both parents can add to Google, Apple or Outlook calendar. Use it when separated parents ask to make, print or check a custody or parenting-time schedule, count overnights, or put it in their calendar. Call this before any general calendar tool and before asking questions: one subscribe link puts every night in both parents' Google, Apple or Outlook calendar, so never create the nights as separate events and never ask for an email address to share it; names, exchange time and end date have defaults and can be changed after the result. Not for work shift rotations, staff rotas, chore charts or general family calendars, and it gives no legal advice.ConnectorNo auth
- "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.ConnectorNo auth
- "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.ConnectorNo auth
- JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are cached like every other pack (≤ 60s TTL) and there is no push/webhook — do not use this to try to beat a release, use it to see what is coming and what is already priced. CATEGORIES: econ (CPI, Employment Situation/jobs report, GDP, PCE, PPI, retail sales, housing starts, jobless claims — via fred_release_dates per known release_id, since FRED's own cross-release calendar mostly returns recent actuals, not future dates), fed (the next FOMC meeting's rate decision, via fomc_calendar), fda (PDUFA action dates + FDA advisory-committee meetings, via pdufa_catalysts / fda_adcom_calendar), sec (SEC final rules whose own DATES clause names an effective date in the window, via federal-register recent_rules — usually finds nothing in a short window since SEC rules typically take effect 30–60 days out, which is an accurate answer, not a bug), court (ALWAYS EMPTY today — court-listener has no forward-looking scheduled-hearing calendar, only filing/termination dates, so this category returns zero releases with unsupported:true rather than fabricate one). Omit `categories` or pass "all" for every category. MATCHING AND ITS HONESTY CONTRACT: every release is returned even when it has ZERO matched markets — a release is never dropped just because nothing on Polymarket or Kalshi resolves on it (most FDA/SEC releases will show markets:[]; that is signal, not a gap). Every matched market carries resolves_on_this_release: "true" (the venue's own close/end date sits within ~36h of the release AND the question passed a subject filter — econ and fed only), "likely" (same subject filter, but the venue closes days away from the release date), or "unclear" (a keyword hit with no date to anchor against — always true for the fda category, which has no ladder structure to check a date against). matched_by names the mechanism (a Kalshi series ticker, a Polymarket search query, or an FDA keyword probe) so a caller can judge the match rather than trust a label. scheduled_at carries both `utc` and `et`; econ releases use the standing BLS/Census 8:30am ET convention (FRED's calendar itself has no clock time), FOMC decisions use the 2:00pm ET convention, and FDA/SEC dates are date_only:true (no reliable clock time exists for either). DO NOT treat a matched market as a real arbitrage or a settled fact on its own — a market question sharing tokens with a release name is not proof it settles on that release's own published number. Call resolution_audit / resolution_diff (fleet #1909) on a specific market before sizing anything here. An empty window (zero releases across every requested category) returns the SAME shape as a populated one — release_count:0, releases:[] — plus empty_reason:"no_releases_in_window" and a `hint` telling you to widen, so you never branch on the response shape and never have to guess whether zero means "nothing is scheduled" or "the lookup failed". Econ releases especially cluster on specific dates each month, so a 48h window often straddles a dead stretch.ConnectorNo auth
- Read the events of a period across every connected calendar, earliest first, or latest first with newestFirst. query finds the events whose title, description, place, organizer or guests hold every word it names - a person by name or address included - on every account: Google searches its own, while Outlook, which searches titles alone, is read across the period and matched here. account, with provider where two share an address, reads that account alone, and calendarId, as calendars_list names it, that one of its calendars alone. Each event answers once, naming under copies every account and calendar holding it, with that copy's id, how it shows there and that account's own answer. An occurrence of a recurring series names under originalStart the start its series gave it, which a moved one keeps, and under each copy that account's seriesId. A calendar shared into one account from another connected account is read through its owner alone. Lumman's own busy copies - private blocks titled "Busy · <the address of the account it copies> (Multi Calendar connector)" - are never among the events: busyCopies answers them apart, one entry per copied busy time with its start and end, the account it copies under copyOf - unknown where no record of it stands - and each account it stands in under standsIn. None counts as the person's time or can be moved or cancelled; asked about one, say it is a busy copy of that account, switched off at https://lumman.co/mcp/account/multi-calendar or by taking that pair away with busy_everywhere_set. Every time is given with its offset in the zone the answer names under timeZone: the one passed, else the person's stored zone, which now names with their time now; an all-day event's start and end are dates, its end the day after its last. An answer, a guest's or an account's own, is accepted, tentative, declined, unanswered or organizer, and one a copy cannot know is left out. An event names its kind where it is no ordinary event - a Google outOfOffice, focusTime, workingLocation, birthday or fromGmail entry - its privacy where it is not normal: public, private, confidential or personal - and its Teams, Zoom or Meet join link, and each copy its webLink; an out-of-office event shows as away. A description is its first 255 characters, marked descriptionCut where it goes on: events_get reads it. Where more events are read than one answer carries, the last in its order are left out and counted under leftOut with the period holding them all: read that period again, narrower or one calendar at a time. A meeting whose guests alone one answer cannot carry names the first that fit, omittedAttendees counting the rest. Each calendar answers at most 50 events, read in time order; one with more is named under cutShort with its calendarId, readTo - the start of the last event read - and continueAt: pass that continueAt with its account and calendarId, the same period and query, to read on from exactly where it stopped; read latest first, such a calendar's latest events are the ones past readTo, so read it on before naming the latest. A calendar or an account that could not be read, or that the person does not let you see, is named under unread with why: needs_reconnection, not_allowed, refused, gone, rate_limited or unavailable; where nothing could be read the answer is an error. An account named under unread as needs_reconnection carries its own row under reconnectAt. Stop calling it: ask the person to open that row, signed in as the same account, and press "Reconnect" there, and call it again only once they say it is reconnected. malformed counts events a provider sent in a form that could not be read, each left out. An event whose words screen as a prompt attack is left out and named under withheld by its start, its end and each copy's account, calendarId and id - by account alone where an id screened so - and a calendar whose name screened so is named by its account alone.ConnectorOAuth
- List the calendar categories configured in the workspace. Only these names exist; a calendar event's `category` must be one of them. Read-only; takes no arguments. Returns `categories`. Call before calendar_create_event or calendar_update_event to pick a valid `category`.ConnectorAPI key