Skip to main content
Glama
local-events-mcp

local-events-mcp

by esdraelon

local-events-mcp

A small MCP server with semantic event tools:

  • list_sources() — show configured sources and whether each source-specific scraper is functional

  • scraper_is_valid(source) — health-check a source-specific scraper and return the extracted semantic payload

  • get_events_for_time_period(source, days, as_of=None) — return semantic events for a source over a time window

  • list_events_by_source_and_date(source, date) — legacy compatibility wrapper for one source on one day

Source config

Edit sources/<source type>/<source>.json to add or update sources. Each source lives in its own file.

Current categories:

  • theater

  • music

  • comedy

  • fairs

  • misc

The server also still understands the legacy sources.json file, but the categorized folder is the preferred layout.

Each source now points at a source-specific Python module under src/local_events_mcp/source_plugins/. The module path is stored in each source JSON and is loaded from disk, so slugs like the-hideout-theatre remain valid.

  • module points at the source-specific plugin module

  • the module exposes scraper_is_valid() and get_events_for_time_period()

  • tools return semantic objects only: title, event type, description, date, location, event URL, price, and metadata

Related MCP server: Evento Public MCP Server

Run

python -m local_events_mcp

Or use the installed console script:

local-events-mcp

Available Tools

4 tools
get_events_for_time_periodC

Return semantic events for a source within the next N days.

Inputs: source (required), days, as_of. Returns: object

list_events_by_source_and_dateC

Return a source's events for one day, including the scraper status.

Inputs: source (required), date (required). Returns: object

list_sourcesB

List sources with functional status and scraper health.

Inputs: no named parameters. Returns: result

scraper_is_validC

Check whether a source-specific scraper is still returning semantic data.

Inputs: source (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get events for a time period, list events for a specific day with scraper info, list sources, and check scraper validity. No overlap in functionality.

    Naming Consistency4/5

    Most tools use a consistent verb_noun pattern in snake_case (get_events, list_events, list_sources), but 'scraper_is_valid' deviates with an adjective instead of a verb, breaking the pattern slightly.

    Tool Count5/5

    4 tools is well-scoped for a local events MCP server. Each tool serves a clear purpose without redundancy, and the count is appropriate for the domain.

    Completeness3/5

    The tool surface covers basic querying of events and source/scraper status but lacks CRUD operations for events and sources (e.g., add source, update event). Notable gaps exist for managing data.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers