GripEventsCtl

An unofficial CLI and MCP server for event apps hosted on Grip. It helps you network at an event you attend, from your terminal or through an AI assistant.

⚠️ Unofficial - Personal Use Only

GripEventsCtl is NOT affiliated with, endorsed by, or supported by Grip. It talks to a Grip-hosted event app with your own attendee session. It is for your own networking at an event you attend.

“Grip” is the name of the event-networking platform run by Intros.at Ltd. This project uses the name only to say which platform your session belongs to.

It is NOT for:

• Spam or unsolicited outreach
• Mass swiping or mass messaging
• Scraping attendee directories into lead lists
• Contacting people outside the platform
• Operating against an account that is not your own
• Any behavior that breaks the platform’s terms or burdens it

If you see misuse of GripEventsCtl, report it as described in Abuse reporting in SECURITY.md.

The friction in the code is on purpose: writes are off by default, repeats are blocked, and the platform’s rate limits are honoured. Do not remove it.

Status

This repository holds the workspace scaffold and, in @gripeventsctl/core, the transport client the commands will use (GripClient: the fixed base URL and header set, the config lookup, the login call, the response envelope and error kinds, the HTTP 429 backoff, paging, one request in flight per process). Of the commands below under “Commands”, the three auth commands, the two events commands, the three attendees commands, match status, the three chat commands, schedule info and the two interest commands exist; attendance get does not; the three writes commands (writes status, writes pending, writes go-ahead) exist too. The no answer interest skip sends is from the app code and is not yet verified live (docs/api/interest.md § Send an answer).

• Nothing is published to npm yet. The npm badges show “not found” until the first release.