mcp-evento
Related Servers
Alternatives to mcp-evento
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables management of Cvent events, registrations, attendees, sessions, contacts, surveys, reports, custom objects, and webhooks via natural language through the Cvent REST API.MIT
- AlicenseAqualityDmaintenanceCreate scheduling polls (like Doodle) from AI agents. Find the best time for meetings, dinners, and events. 5 tools: create_poll, get_poll, vote_on_poll, get_results, finalize_poll. No authentication required.571 npm1MIT

WebAsk MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create and validate surveys, distribute them, read and tag responses, and generate reports or exports through a hosted Streamable HTTP MCP endpoint with API-key authentication.MIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage no-login scheduling polls, collect Yes/No availability, and set or close final decisions through MCP tools.-
- AlicenseBqualityDmaintenanceEnables interaction with the Wisembly API to fetch and manage event data, including event details, participants, organizers, and locations.21ISC
- AlicenseAqualityBmaintenanceCalendar API purpose-built for AI agents. Exposes tools to manage agents, calendars, and events, find meeting times, run scheduling proposals, set availability rules, manage webhooks, and subscribe to iCal feeds.65746 npmApache 2.0
TDQS
Scored across 24 tools
Most tools target distinct resources and actions (lister/obtenir/creer/modifier/clore/supprimer_sondage, response and calendar tools are clearly separated). The main confusion is the trio conflits_sondage, creneaux_incompatibles and creneaux_compatibles, which all compute survey-vs-calendar overlap and differ only in output framing; obtenir_sondage vs ouvrir_sondage is also a subtle distinction (data vs browser window).
Names are consistently snake_case French with a predictable verb_noun pattern for the action tools (lister_, obtenir_, creer_, modifier_, supprimer_, ajouter_, repondre_). A handful of noun-first names (resultats_sondage, reponses_participant, reponses_question, conflits_sondage, creneaux_compatibles) break the verb-first convention but remain readable and unambiguous.
24 tools is heavy for the apparent scope; the survey CRUD, response, participant and calendar groups each earn their place, but the three conflict/compatibility tools overlap enough that one or two could be folded in, and clore/rouvrir could arguably be state changes on modifier_sondage.
Survey lifecycle (create, read, list, update, close, reopen, duplicate, delete) and response reading are well covered, with calendars and conflict detection adding real value. However, invitation/participant management is missing (creer_sondage explicitly sends no invitations, and there is no tool to invite or add participants), and there is no way to delete or retract a submitted response.