Allows AI agents to work within a user's signed-in Meetup account to create, copy, duplicate, and manage events, including setting dates, venues, RSVP limits, hosts, online links, and moving events between groups.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@meetup-mcp Copy last week's Python Night event to every Tuesday in April at 6:30 pm."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Yes, Claude, ChatGPT and other AI agents can work in your Meetup account. The official Meetup app in ChatGPT helps people discover events by interest, location and date. Cotlet.dev connects your own signed-in Meetup account to any AI agent, so you can ask in plain words and the AI creates and copies events for you.
Create a "Founders Coffee" event in my Austin Startups group for Thursday, March 12 at 8 am at Epoch Coffee, limit 25 RSVPs.
Copy last week's "Python Night" event to every Tuesday in April at 6:30 pm, same venue and description.
Duplicate our Saturday hike event, change the trail to Barton Creek and set the start to 9 am.
Create a free online workshop called "Intro to Email Marketing" on May 7 at 1 pm with a Zoom link and 3 hosts: me, Priya and Tom.
Copy the "Spring Networking Mixer" event into my Dallas group and move it to Friday, June 5 at 7 pm.
Related MCP server: meetup-mcp-server
Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.
Copy .cursor/mcp.json from this repo into your project:
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}This repo is a real MCP server. It speaks MCP over stdio, lists its Meetup tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
{"mcpServers":{"meetup":{"command":"uvx","args":["meetup-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}Or with Docker:
docker build -t meetup-mcp .
docker run -i --rm -e COTLET_API_KEY meetup-mcpTools: meetup_guide, meetup_status, meetup_open, meetup_read, meetup_click, meetup_type, meetup_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
Python 3.10+, nothing else to install. From PyPI:
pip install meetup-mcp # or run it once: uvx meetup-mcp connect
meetup-mcp connectOr straight from this repo:
export COTLET_API_KEY="your-key"
python3 meetup_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 meetup_agent.py status # is Meetup ready in your Cotlet.dev account
python3 meetup_agent.py guide # Meetup screens and sign-in link
python3 meetup_agent.py read # open Meetup, read the page, close the browser
python3 meetup_agent.py tools # list Cotlet.dev tools
python3 meetup_agent.py serve # start the stdio MCP server (same as no argument)Does Meetup have an API?
Meetup has a GraphQL API, but only members with an active Meetup Pro subscription can get access, and it stops working when Pro lapses (checked 11 Oct 2026). Even with Pro it cannot message members, copy events or manage attendees. Cotlet.dev works in your own signed-in Meetup account, so your AI agent can create and copy events with no API key and no code.
How do I connect Meetup to ChatGPT?
The official Meetup app in ChatGPT is for discovering events. To create and copy events in your own account, add Cotlet.dev as an app in ChatGPT (Settings → Apps, connector URL https://cotlet.dev/mcp/v1), sign in to Meetup once in your Cotlet.dev Cloud Browser, and ask ChatGPT in plain words. No code and no Meetup API key.
Is there a way to use Claude with Meetup?
Yes. In Claude Code run the one-line claude mcp add command above; in the Claude app add https://cotlet.dev/mcp/v1 as a custom connector. Claude then works in your own Meetup account.
Is there a Meetup MCP server?
Yes. Cotlet.dev is a hosted MCP server that works in Meetup for you, 24/7, with Claude, ChatGPT, Cursor, Codex, n8n, Make and Zapier.
Start free: https://cotlet.dev/signup?app=meetup&utm_source=github&utm_medium=readme&utm_campaign=meetup
Click a numbered element on the current Meetup page.
Inputs: element (required).
Close the Meetup browser session when the work is done, so credits stop running.
Inputs: no named parameters.
How to work in Meetup (create and copy events): its screens and the sign-in link. Call this first.
Inputs: task.
Open a Meetup page in your signed-in Cloud Browser (default https://www.meetup.com) to work with create and copy events.
Inputs: url.
Read the current Meetup page: its text and numbered buttons, links and fields.
Inputs: element.
Check that your Cotlet.dev account and Meetup are ready: account, credits and Meetup connection.
Inputs: no named parameters.
Type text into a numbered field on the current Meetup page.
Inputs: text (required), element (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Run ticketed events from your AI assistant: create events, sell tickets via Stripe, check in.
