Official MCP RegistryListed
SFomo: Bay Area events
Read-only search of upcoming SF Bay Area events: AI/tech, dance, music, arts, food, fitness.
First seen 8 Oct 2026. Evidence as of 20 Oct 2026.
6
Tools
From an anonymous probe
1
Source listings
Each with its own history
35
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| create_custom_calendar | Build a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on SFomo (open_on_sfomo; give the user this first), subscribe links (Google Calendar, Apple/Outlook webcal, plain .ics) and a preview. The calendar refreshes itself every few hours, so new matching events keep appearing. An event is included if it matches ANY interest and no exclude term. Nothing is stored by SFomo: the interests are encoded in the link itself. Interview the user first (see the custom_calendar prompt), check matches with search_events, and call this again to adjust. For a one-off answer rather than a standing calendar, use search_events. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour. | Read-only |
| find_performer | Find a performer, band, comedian or act in Bay Area by name (words in `query` must all match; case-insensitive) and get their upcoming events, top venues, genres or topics and the platforms that list them. Names come only from public event listings; there are no contact details. Use it for "when is <band> playing" or "who plays at <venue>". For events by topic or venue rather than by name, use search_events; use get_event with an id for one event's full listing. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour. | Read-only |
| get_city | Get what SFomo covers in Bay Area: how many upcoming events it lists and for which dates, when the data was last published, how many sources feed it, and upcoming events per category, topic, neighborhood and town. Call it before searching to pick valid category, topic, neighborhood and town values, or to tell a user what this site covers; it returns counts only, no events (use search_events or list_upcoming for those). Takes no arguments. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour. | Read-only |
| get_event | Get the full listing for one upcoming event by the `id` that search_events, list_upcoming or find_performer returned: title, dates, venue, price (all-in, or "See tickets"), the original listing (`link`), every source that lists it and first_seen / last_seen / last_fetched dates. Ids stay the same while an event is listed; a past or removed event returns an error, so search again. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour. | Read-only |
| list_upcoming | Browse the next N days of events day by day, with no search words. `by_day` counts every match per date, and when more events match than `limit` the rows are spread evenly across the days (earliest first within each day), so each day is represented. Use it for overviews like "what's happening this week"; for search words, free-only, a town or exact from/to dates use search_events, and for one event's details get_event. Optional filters: one category or topic, an audience, and a place: `neighborhood` keeps events inside a named area (radius_km widens it past the boundary), `near` ranks events by distance from a place or "lat,lon" within radius_km. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour. | Read-only |
| search_events | Search every upcoming Bay Area event by words, dates, price, topic or place: dance, AI, music, arts, food, sports, comedy, exercise, volunteering, dating, business and professional networking. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, for one act by name find_performer. All words in `query` must appear in the title, venue, performers, organizer or tags; dates are local (America/Los_Angeles), YYYY-MM-DD. Results come earliest first, at most `limit`; `count` says how many matched in total, so narrow the search rather than paging. get_city lists valid neighborhood, town, category and topic values. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour. | Read-only |
Change history
- search_events: input schema changed (+audience, +biz_format, +sector)
- search_events: description changed (+"every" +"event by words, dates, price, topic or place: dance," +"volunteering, dating, business and professional networking. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, for one act by name find_performer.")
- list_upcoming: input schema changed (+audience, +biz_format, +sector)
- list_upcoming: description changed (+"Browse" +"events day by day, with no search words." +"date, and")
- get_event: input schema changed
- get_event: description changed (+"Get the full listing for" +"the" +"that search_events, list_upcoming or find_performer returned: title, dates, venue, price (all-in, or "See tickets"), the original listing (`link`), every")
- get_city: tool added
- find_performer: input schema changed
- find_performer: description changed (+"For events by topic or venue rather than by name, use search_events; use" +"No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour." -"Use")
- create_custom_calendar: input schema changed (+include_seniors)
- create_custom_calendar: description changed (+"For a one-off answer rather than a standing calendar, use search_events. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.")
- server instructions changed (+"id; get_city lists the valid neighborhood, town, category and topic values with counts." -"id.")
- search_events: title changed
- search_events: input schema changed (+near, +neighborhood, +radius_km)
- search_events: annotations changed
- list_upcoming: title changed
- list_upcoming: input schema changed (+limit, +near, +neighborhood, +radius_km)
- list_upcoming: description changed (+"category, topic or place. `by_day` counts every match per date; when there are more than `limit`, the rows shown are spread across the days (earliest first within each day), so narrow with category, topic or place, or page a single day with search_events from/to." -"category.")
- list_upcoming: annotations changed
- get_event: title changed
- get_event: annotations changed
- find_performer: tool added
- create_custom_calendar: title changed
- create_custom_calendar: input schema changed
- create_custom_calendar: annotations changed
- server instructions changed (+"For "in <neighborhood>" use neighborhood (a neighborhood or town name); for "near <place>" use near (a neighborhood, town, venue name or "lat,lon") with radius_km. Results then carry distance_km, and place.unplaced_events counts events left out because their venue isn't mapped.")
- search_events: input schema changed
- search_events: description changed (+"dating)." +"title/location/performers/organizer/tags." +"local (America/Los_Angeles),")
- list_upcoming: input schema changed
- get_event: tool added
- create_custom_calendar: input schema changed
- server instructions changed (+"SFomo (https://sfomo.ai)." +"category, topic" +"scope.")
- create_custom_calendar: tool added
- server instructions changed (+"To make the user a self-updating calendar of their interests, follow the custom_calendar prompt and call create_custom_calendar.")
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | ai.sfomo/events | 8 Oct 2026 | 20 Oct 2026 | 1 |