Weezevent MCP server for ChatGPT and Claude
Connect Weezevent to ChatGPT, Claude and other AI agents through Cotlet.dev. Work with events, orders, attendees, discount codes, invitations and refund requests in your own signed-in account.
Request access: https://cotlet.dev/signup?app=weezevent
Cotlet.dev is independent and is not affiliated with, endorsed by or sponsored by Weezevent.
Connect ChatGPT and Claude
Sign in to Weezevent in its Cotlet Cloud Browser and enable it for agents.
In ChatGPT, open Settings > Apps & Connectors > Create. Set the MCP server URL to https://cotlet.dev/mcp/v1/connect and use OAuth to sign in to Cotlet.dev.
In Claude, open Settings > Connectors > Add custom connector. Set the URL to https://cotlet.dev/mcp/v1/connect and sign in to Cotlet.dev.
For Codex, Claude Code and other clients that use a key, use https://cotlet.dev/mcp/v1 with an Authorization: Bearer header containing your Cotlet API key.
Install the Python stdio adapter
Requires Python 3.10 or later, with no third-party runtime dependencies.
pip install weezevent-mcp
export COTLET_API_KEY="your-cotlet-api-key"
weezevent-mcp serve
Get your Cotlet API key at https://cotlet.dev/app. Keep it in your environment or client credential store.
{"mcpServers":{"weezevent":{"command":"weezevent-mcp","args":["serve"],"env":{"COTLET_API_KEY":"your-cotlet-api-key"}}}}
What the adapter exposes
The adapter exposes seven browser helpers: weezevent_guide, weezevent_status, weezevent_open, weezevent_read, weezevent_click, weezevent_type and weezevent_close.
Call weezevent_guide first for guidance on the task. The helpers forward calls to the hosted Cotlet.dev server. Without a key, calls explain where to obtain one. They require your own Weezevent account connected in Cotlet.dev.
The live Weezevent integration page separately documents 13 hosted workflow operations, including listing events, orders and attendees, reading participation reports, creating discount codes, sending invitations and requesting refunds. These workflow operations are distinct from the adapter's seven browser helpers. Hosted write operations ask for approval by default.
Example requests
- List orders for the event I select and show unpaid reservations.
- List attendees by ticket source and promo code.
- Draft a discount code, invitation or refund request for my approval.
Command line
weezevent-mcp connect
weezevent-mcp status
weezevent-mcp guide
weezevent-mcp read
Metadata
Release files for weezevent-mcp 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| weezevent_mcp-1.1.0.tar.gz | 7.1 kB | Without provenance | Details for weezevent_mcp-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| weezevent_mcp-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for weezevent_mcp-1.1.0-py3-none-any.whl |
Total release size: 14.9 kB
Release files / weezevent_mcp-1.1.0.tar.gz
| Download URL | weezevent_mcp-1.1.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13bd0596ffd26843bcc8f1ba1435890ca803ecff45d7d22fa732fc11f607ec81
|
|
BLAKE2b-256 checksum How to use checksums |
fc9fd254a47d91e98cb06c1b88981fdcacf6d8931ae6dc3f7410b01d1e8f7246
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / weezevent_mcp-1.1.0-py3-none-any.whl
| Download URL | weezevent_mcp-1.1.0-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d159b7c4c646375d6082264e45451c052d0021572100ba3bc563004e24b7f254
|
|
BLAKE2b-256 checksum How to use checksums |
0c33008c6abddd13c6b6a252849d1b1294403db343ec4b4693185df986b1409f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for weezevent-mcp 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.