EventMatey Event Discovery
Find public EventMatey events that organisers have approved for AI discovery.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~1,350Tokens (tool definitions)
~3.6 KBTypical response size
Moderate attention impact (1.05% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"event-discovery": {
"url": "https://mcp.eventmatey.com/mcp"
}
}
}Remote endpoints
https://mcp.eventmatey.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_events_by_keyword(keyword, location_text, start_date, end_date, categories, ...)
Search public EventMatey events by keyword, optional UK location text, date range, categories, and price range. Returns only published and bookable events that the organiser has enabled for AI discovery.
Input Schema
{
"type": "object",
"properties": {
"keyword": {
"description": "Keyword or phrase to search for, such as baking class or live music",
"type": "string",
"minLength": 1,
"maxLength": 120
},
"location_text": {
"description": "Optional UK location hint such as Bristol, Manchester, or London",
"type": "string",
"minLength": 1,
"maxLength": 160
},
"start_date": {
"description": "Optional inclusive start date in YYYY-MM-DD format",
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
},
"end_date": {
"description": "Optional inclusive end date in YYYY-MM-DD format",
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
},
"categories": {
"description": "Optional category or tag filters",
"maxItems": 10,
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 40
}
},
"min_price_gbp": {
"description": "Optional minimum price in GBP",
"type": "number",
"minimum": 0,
"maximum": 100000
},
"max_price_gbp": {
"description": "Optional maximum price in GBP",
"type": "number",
"minimum": 0,
"maximum": 100000
},
"limit": {
"description": "Maximum number of events to return",
"default": 10,
"type": "integer",
"minimum": 1,
"maximum": 25
}
},
"required": [
"keyword"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢search_events_nearby(latitude, longitude, radius_km, location_text, start_date, ...)
Search EventMatey events by location. The current v1 implementation uses location_text plus date/category/price filters. Latitude/longitude and radius are accepted for forward compatibility but are not yet used for true distance search.
Input Schema
{
"type": "object",
"properties": {
"latitude": {
"description": "Optional latitude for future geo-capable search",
"type": "number",
"minimum": -90,
"maximum": 90
},
"longitude": {
"description": "Optional longitude for future geo-capable search",
"type": "number",
"minimum": -180,
"maximum": 180
},
"radius_km": {
"description": "Optional search radius in kilometres for future geo-capable search",
"type": "number",
"minimum": 1,
"maximum": 250
},
"location_text": {
"description": "Use this for the current v1 location search, such as Bristol or Leeds",
"type": "string",
"minLength": 1,
"maxLength": 160
},
"start_date": {
"description": "Optional inclusive start date in YYYY-MM-DD format",
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
},
"end_date": {
"description": "Optional inclusive end date in YYYY-MM-DD format",
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
},
"categories": {
"description": "Optional category or tag filters",
"maxItems": 10,
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 40
}
},
"min_price_gbp": {
"description": "Optional minimum price in GBP",
"type": "number",
"minimum": 0,
"maximum": 100000
},
"max_price_gbp": {
"description": "Optional maximum price in GBP",
"type": "number",
"minimum": 0,
"maximum": 100000
},
"limit": {
"description": "Maximum number of events to return",
"default": 10,
"type": "integer",
"minimum": 1,
"maximum": 25
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_event_details(event_id)
Get fuller public details for one discoverable EventMatey event, including the canonical hosted booking URL.
Input Schema
{
"type": "object",
"properties": {
"event_id": {
"description": "EventMatey event UUID",
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$"
}
},
"required": [
"event_id"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence
Recent observations
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools