Weezevent MCP Server
Related Servers
Alternatives to Weezevent MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects AestheticsPro accounts to ChatGPT, Claude, and other AI agents through Cotlet, enabling appointment scheduling, client contact access, lead creation, and staff assignment with user approval.7Elastic 2.0
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude and other AI agents to work inside a signed-in Eversports Studio Manager account through Cotlet — viewing studio activities and sign-in lists, signing participants in, pausing or resuming memberships, and emailing invoices, with user approval before any change is saved. It runs as a hosted connector or a local stdio server that forwards tool calls to Cotlet.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents like ChatGPT, Claude, and Cursor to work inside a user's own signed-in Exercise.com account, viewing schedules, booking sessions, messaging clients, and handling invoices with approval steps. It runs as a hosted connector or a local stdio server that forwards tool calls to the hosted backend using a Cotlet API key.Elastic 2.0

OutcomeCI MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create, validate, and manage agent-powered workflows across team tools, with tools for inspecting schemas, configuring triggers, and reviewing runs and logs. It provides authorized remote access through OAuth without local installation or shared API keys.1MIT- AlicenseNot gradedqualityBmaintenanceLets Claude, ChatGPT or Cursor connect to PrestaShop, with each employee approving what they may do.2Academic Free v3.0
- AlicenseAqualityCmaintenanceEnables ChatGPT, Claude, and other AI agents to draft estimates, schedule jobs, assign crew members, and review receivables in a user's signed-in business account, requiring approval before actions reach other people.7Elastic 2.0
TDQS
Scored across 7 tools
Each tool maps to a clearly distinct phase or action: guide/status for setup, open/close for session lifecycle, and read/click/type for page interaction. There is no meaningful overlap between tools, and the intended sequence is easy to infer.
All tools use the same weezevent_ prefix and snake_case convention. The action names are short and predictable, with guide/status serving as clearly identifiable meta-tools alongside the browser actions.
Seven tools is well-scoped for a browser automation server covering setup, session lifecycle, and core page interaction. Each tool has a clear role, and there are no redundant or filler tools.
The set covers the essential browser workflow: checking readiness, opening a session, reading the page, clicking, typing, and closing. Minor gaps exist around explicit navigation, scrolling, waiting, or select-field handling, but most tasks can be worked around using read/click/type.