meetup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for the local stdio server; without it, tool calls fail with "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Meetup through Cotlet.dev. Call meetup_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 |
|---|---|
| meetup_guideA | How to work in Meetup (create and copy events): its screens and the sign-in link. Call this first. |
| meetup_statusA | Check that your Cotlet.dev account and Meetup are ready: account, credits and Meetup connection. |
| meetup_openB | Open a Meetup page in your signed-in Cloud Browser (default https://www.meetup.com) to work with create and copy events. |
| meetup_readB | Read the current Meetup page: its text and numbered buttons, links and fields. |
| meetup_clickB | Click a numbered element on the current Meetup page. |
| meetup_typeB | Type text into a numbered field on the current Meetup page. |
| meetup_closeA | Close the Meetup 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 distinct action in a browser automation loop: guide/status are pre-flight, open/close frame the session, and read/click/type are the core interaction triad. The only slight overlap is meetup_guide vs meetup_status, since both are onboarding-style checks called before doing work, but their described purposes (usage instructions vs account/connection readiness) are clear enough to separate.
All seven tools follow the exact same pattern: the meetup_ prefix plus a single lowercase verb (guide, status, open, read, click, type, close). No mixing of conventions, casing, or verb styles.
Seven tools is tightly scoped for a browser-driven Meetup automation server, and every tool earns its place: two setup helpers, open/close lifecycle, and the read/click/type interaction primitives. Nothing appears redundant or padded.
The surface covers the full session lifecycle plus the essential read→click/type loop needed to create and copy events, with guide and status covering onboarding. Minor gaps exist for a browser automation domain—no explicit scroll, navigate-to-URL, wait, or screenshot tool—which could be limiting on long pages, but agents can largely work around this via clicking links.