Weezevent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | No | Your Cotlet API key, available at https://cotlet.dev/app. Export it as COTLET_API_KEY. Without it, a tool call explains where to get a key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Weezevent through Cotlet.dev. Call weezevent_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weezevent_guideA | How to work in Weezevent (prepare estimates and manage jobs and crew assignments): its screens and the sign-in link. Call this first. |
| weezevent_statusA | Check that your Cotlet.dev account and Weezevent are ready: account, credits and Weezevent connection. |
| weezevent_openB | Open a Weezevent page in your signed-in Cloud Browser (default https://www.weezevent.app) to work with prepare estimates and manage jobs and crew assignments. |
| weezevent_readA | Read the current Weezevent page: its text and numbered buttons, links and fields. |
| weezevent_clickC | Click a numbered element on the current Weezevent page. |
| weezevent_typeB | Type text into a numbered field on the current Weezevent page. |
| weezevent_closeA | Close the Weezevent browser session when the work is done, so credits stop running. |
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 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.