Philly Events MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port to listen on when running with the HTTP transport (e.g. 3000). | |
| TRANSPORT | No | The transport mode for the server. Set to "http" to run with HTTP (production). Defaults to stdio for local development. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| philly_search_eventsA | Search for events across all Philadelphia event sources (Do215, Visit Philly, Eventbrite). This is the primary tool for discovering events happening in Philadelphia. It aggregates results from multiple sources, deduplicates them, and allows filtering by various criteria. Args:
Returns: Aggregated event listings from all sources with deduplication. Examples:
|
| philly_search_sourceA | Search for events from a specific Philadelphia event source. Use this when you want to search only one source (e.g., just Do215 or just Eventbrite) rather than aggregating from all sources. Args:
Available sources:
|
| philly_export_to_calendarA | Convert Philadelphia events to Google Calendar format for import. This tool takes event IDs (from search results) and returns them in Google Calendar JSON format, ready for import via the Google Calendar API. Args:
Returns: Array of Google Calendar event objects ready for API import. Example workflow:
|
| philly_list_categoriesA | List all available event categories for filtering Philadelphia events. Use this to discover what categories are available when searching for events. |
| philly_list_neighborhoodsA | List all recognized Philadelphia neighborhoods for filtering events. Use this to discover what neighborhood filters are available. |
| philly_weekly_digestA | Generate a curated weekly digest of Philadelphia events. This tool searches for events happening in the next 7 days and formats them as a digestible newsletter-style summary, organized by category. Args:
Perfect for:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: discovery (list_categories, list_neighborhoods), search (search_events aggregate, search_source single-source), export, and digest. The aggregate vs single-source search distinction is clearly explained. philly_weekly_digest partially overlaps with philly_search_events since it's essentially a preset filtered search with formatting, but the newsletter framing keeps it distinguishable.
All tools use a consistent philly_ prefix followed by a verb_noun pattern (list_categories, search_events, export_to_calendar, weekly_digest). No mixing of conventions or casing styles.
Six tools is well-scoped for a niche city event aggregator, with each tool earning its place: discovery, search, single-source search, export, and digest. No redundant or trivial tools in the set.
The surface covers discovery, search, filtering, export, and digest workflows well. The one noticeable gap is a get_event-by-ID tool, which would be useful given that export_to_calendar consumes event IDs yielded by search.