eventor-mcp
Related Servers
Alternatives to eventor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceExposes the OpenProject REST API as MCP tools for project management, including creating and managing projects, work packages, relations, attachments, users, notifications, watchers, boards, and reference data.3725 npmMIT
- FlicenseAqualityDmaintenanceMCP server to list and get events from Evento's public API using an API key.21-
- AlicenseBqualityAmaintenanceMCP server providing typed tools for Norwegian public data sources, enabling natural language queries to official datasets like SSB, Brønnøysund, MET, Kartverket, Entur, and more, without requiring API keys.47MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that exposes Estonian eesti.ai events (workshops and meetups) via search, upcoming, and single event tools, wrapping the vportal.ee search API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Nettskjema forms, submissions, invitations, and data export through the MCP protocol.MIT
- FlicenseCqualityCmaintenanceEnables interaction with the Edookit school management system API, exposing attendance, lessons, people, grades, payments, courses, timetable, and individual goals as MCP tools.46-
TDQS
Scored across 8 tools
Most tools target distinct resources (events, organisations, classes, imports), and the descriptions clarify scope. However, get_event_entries, get_competitors, and get_entry_changes all concern 'who is participating' and differ mainly by scope (event vs club vs timestamps), which could cause occasional misselection.
All eight tools follow a clean snake_case verb_noun pattern using get_, list_, and import_ prefixes consistently. The convention is predictable and easy to reason about.
Eight tools is well-scoped for an orienteering event data server, with a sensible split between read operations and two publish/import writes. Each tool clearly earns its place.
The surface covers the core lifecycle: listing events/organisations, reading classes, entries, competitors, and publishing start/result lists. Minor gaps exist, such as no single-event detail fetch and no update/delete of entries, but agents can work around these.