Read WaiverFile waivers, events, forms and SMS opt-ins; create and update events, invite managers. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"waiverfile": {
"url": "https://waiverfile.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"waiverfile": {
"type": "http",
"url": "https://waiverfile.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your WaiverFile API key and WaiverFile Site ID.
In WaiverFile open Settings → API → API keys. Click Create a Key if you have none, click Show to reveal the key, and copy the Site ID shown below it. The key gives access to your signers' personal data and can create events; revoke it there at any time. Your key is used only to call the WaiverFile API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your WaiverFile API key and WaiverFile Site ID. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the WaiverFile connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
waiverfile_get_site | read | Get site details Details of the WaiverFile site (WaiverSite) this API key belongs to: name, settings and plan information as WaiverFile reports them. GET /GetSiteDetails. |
waiverfile_list_waiver_forms | read | List waiver forms List the waiver forms of the site (name, id, which fields they collect: email, address, phone, date of birth, minimum age, signature). Active forms by default; set include_deleted for all forms including deleted ones. Use the form ids when creating or updating events. GET /GetActiveWaiverForms or /GetAllWaiverForms. |
waiverfile_list_events | read | List events by date range List waiver events (a class, tour, party or session that collects waivers) whose date falls in a range, optionally only one event category. Each event has an id, name, start/end, headcount and spots remaining. Dates are UTC. GET /GetEventsByDateRange or /GetEventsByCategory. |
waiverfile_list_upcoming_events | read | List upcoming events List upcoming waiver events between two dates (UTC), for example the next 7 days. GET /GetUpcomingEvents. |
waiverfile_list_event_categories | read | List event categories List the event categories of the site (id and name). Use the ids to filter events or to put a new event in a category. GET /GetEventCategories. |
waiverfile_get_event_waivers | read | Get waivers for an event The waivers collected for one event: who signed, when, and the participants. Personal data of signers. GET /GetWaiversForEvent. |
waiverfile_search_waivers | read | Search waivers Search signed waivers by free-text terms (a signer's name, email or phone). Personal data of signers. GET /SearchWaivers. |
waiverfile_get_waiver | read | Get a waiver One signed waiver by id: signer, date signed, participants, collected form data, event and the agreement text. Set lite for only the collected form data (no agreement text or event info). Signature and image bytes are never returned. GET /GetWaiver or /GetWaiverLite. |
waiverfile_find_waivers_by_reference | read | Find waivers by reference id Find waivers by the reference ids an outside booking or reservation system attached to them (referenceID1, 2, 3). Give at least one of reference_id_1/2/3, or reference_id_any to match all three fields. GET /GetWaiversByReferenceID. |
waiverfile_list_waivers | read | List waivers by date range A page of the waivers signed in a date range. Set lite for only the collected form data (smaller). For a flat export with custom form columns use waiverfile_export_waiver_data; for totals use waiverfile_count_waivers. Personal data of signers. GET /GetAllWaiversByDateRange or /GetAllWaiversByDateRangeLite. |
waiverfile_export_waiver_data | read | Export waiver data A page of flat waiver rows for a date range (the data behind the WaiverFile export): standard fields, optionally every custom form field as a column, and participants either as one comma-separated column or one row each. Personal data of signers. GET /GetWaiverData. |
waiverfile_count_waivers | read | Count waivers in a date range How many waivers a date range holds: record_count (GetWaiverDataCount, the rows waiverfile_export_waiver_data pages through) and waiver_count (GetAllWaiversByDateRangePageCount, which WaiverFile documents as the number of waivers in the range, used to work out the pages of waiverfile_list_waivers). pages_at_page_size is waiver_count divided by page_size (default 25), rounded up. GET /GetWaiverDataCount and /GetAllWaiversByDateRangePageCount. |
waiverfile_list_sms_subscribers | read | List SMS subscribers SMS marketing subscribers (phone numbers) that opted in during a date range, or with opted_out set the ones that opted out. Dates are UTC. Personal data. GET /GetSubscribersByDate or /GetOptedOutSubscribersByOptOutDate. |
waiverfile_create_event | write | Create an event Create a waiver event (a class, tour or session that collects waivers) with a name and a start/end time (UTC). Optionally an all-day flag, category, location, signing cut-off, participant limit and which waiver forms to attach (default: WaiverFile's own choice, see list_waiver_forms). Not idempotent: calling twice creates two events. Sends no email. POST /InsertEvent. |
waiverfile_update_event | write | Update an event Update an existing event. WaiverFile replaces the whole event, so name, start, end and all_day are required and anything left out is reset: category_id empty = no category, waiver_form_ids empty = ALL active forms are attached. Read the event first (waiverfile_list_events) and send its current values for the fields you do not change. Same input twice gives the same result. POST /UpdateEvent. |
waiverfile_invite_event_managers | write | Invite event managers SENDS EMAIL: invites people (by email address) to manage one event; they can log in to WaiverFile and see its signers and participants, with the fields set in the account settings. WaiverFile emails each address, with your optional message in the body (skip_email_if_account_exists suppresses the email for people who already have an account). Cannot be undone by this server except with the vendor's own remove-managers action. Requires confirm=true after the user approved it. POST /InviteEventManagers. |
waiverfile_create_event_category | write | Create an event category Create an event category (a label to group events). Not idempotent: calling twice with the same name creates two categories. POST /InsertEventCategory. |
waiverfile_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
waiverfile_request_feature | Request a missing feature Tell usefulapi that the user needs something the WaiverFile tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
waiverfile_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on WaiverFile (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
waiverfile_cancel_subscription | Cancel the Pro subscription Cancel the caller's WaiverFile Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run waiverfile_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this WaiverFile server only. Subscribe with waiverfile_upgrade (it returns a Stripe Checkout link). Cancel any time with waiverfile_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running waiverfile_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by WaiverFile. The server calls the WaiverFile API with your own WaiverFile access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your WaiverFile API key and WaiverFile Site ID. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your WaiverFile API key and WaiverFile Site ID. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the WaiverFile API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in WaiverFile.
Yes, if you approve it. 4 of the 17 WaiverFile tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this WaiverFile server only. Cancel any time: Pro then runs to the end of the paid period. Run waiverfile_usage_status to see how many calls you used.
Ask the AI to run waiverfile_upgrade: it returns a Stripe Checkout link. To cancel, run waiverfile_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with waiverfile_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.