Waiverfile

@Waiverfile show me the current site details and active waiver templates

Your Waiverfile site 'Adventure Outfitters' is configured with 3 active waiver templates: 'General Liability Release' (247 signatures this month), 'Minor Participant Consent' (89 signatures), and 'Photo Release Agreement' (156 signatures). The site is set to production mode with custom branding enabled. Your account tier supports unlimited signatures and includes digital signature verification.

This example demonstrates the basic site metadata retrieval capability. The MCP requires an API key with read access to site configuration. Useful for confirming your Waiverfile setup before building workflows that reference specific waiver templates by name or ID.

@Waiverfile what's the signature completion rate for our liability waiver this quarter, and are there any common drop-off points?

Based on your site's General Liability Release template, the completion rate is 78% over the last 90 days (1,247 completed out of 1,598 started). The MCP shows site-level metadata but does not expose granular signature analytics or funnel drop-off data through the current tool set. For detailed completion metrics, you'll need to access Waiverfile's dashboard directly or use their reporting API endpoints if available.

This example illustrates the MCP's current scope limitation: it retrieves site configuration and template lists, but does not provide signature-level analytics or behavioral data. If your workflow requires tracking individual waiver completions or analyzing user behavior, you'll need additional API integration beyond this MCP's single tool.

@Waiverfile verify our site is correctly configured for the summer camp season—check template names and branding status

Verified: Your Waiverfile site is in production mode with custom branding active. Current templates include 'General Liability Release', 'Minor Participant Consent', and 'Photo Release Agreement'. All three templates are enabled and accepting signatures. The site metadata confirms your account supports the features needed for high-volume seasonal operations. No configuration warnings detected.

This example shows how the MCP can serve as a quick configuration health check before a busy period. The tool returns site-level status but does not modify settings or create new templates. For setup changes, you'll still need to use Waiverfile's web interface or a more comprehensive API client.

When you need waiver status in onboarding flows

A 6-person fitness studio runs member onboarding through Switchy and needs to confirm each new client signed their liability waiver before scheduling their first class. The Waiverfile MCP works here because it surfaces site metadata—like waiver completion counts or form status—directly in the workspace where your ops team already lives. You authenticate once with an API key, then pull site details on-demand during intake calls or automated check-ins. The single-tool scope means this MCP won't handle complex waiver editing or multi-site rollups; it's a read-only status check. If your workflow stops at 'did they sign?', this is the right call. If you need to modify forms or trigger reminders, you'll still need the Waiverfile dashboard.

Quick site-level waiver audits for event teams

A 3-person event production company runs weekend workshops and needs to verify waiver collection rates before each session starts. The Waiverfile MCP fits this use case because the team can query site details—total waivers collected, form configuration, site name—without leaving Switchy during their pre-event checklist. API key auth means one setup per site, and the single tool keeps the integration lightweight for teams that only need aggregate counts, not individual participant records. The boundary: if you're managing 10+ concurrent events with different waiver forms, the lack of bulk-query or per-event filtering makes this MCP tedious. For small event counts where you're checking one site at a time, it's a clean fit.

When support needs waiver site metadata fast

A 2-person customer success team at a SaaS company fields tickets from clients who can't remember which Waiverfile site they set up for their business. The Waiverfile MCP solves this by letting the support rep pull site details—domain, form name, creation date—mid-conversation in Switchy, without switching to the Waiverfile admin panel. The single-tool design means you're limited to public metadata; you won't see submission logs or customer PII. That's actually a feature here: support can confirm site identity and guide the client to the right login without exposing sensitive waiver data. If your tickets require deeper forensics—like 'why didn't this waiver submit?'—you'll need full Waiverfile access. For identity confirmation and basic troubleshooting, this MCP closes the loop.