Troubleshooting the Claude + WaiverTrail MCP Connector (OAuth, Tools, Sends)
Fix common Claude MCP issues with WaiverTrail: auth window problems, tools not loading, token errors, and send failures. Symptom-based checklist before you contact support.
Article preview
Designed for quick scanning: key takeaways, interactive comparison blocks, and direct previews to related platform pages.
Key takeaways
- ## Start here: confirm the basics
- Most connector issues are URL, browser, or session state—not mysterious AI failures
- If this is your first install, walk the happy path in order using the [setup guide](/blog/waivertrail-claude-mcp-send-waivers-seconds) before deep troubleshooting.
Support specialist troubleshooting on laptop
In this article
Start here: confirm the basics
Most connector issues are URL, browser, or session state—not mysterious AI failures. Confirm you are using the current HTTPS MCP endpoint from the integration hub, that your WaiverTrail account is active, and that you completed the browser Authorize step after Claude opened the login tab.
If this is your first install, walk the happy path in order using the setup guide before deep troubleshooting.
Symptom: connected but tools or lists are empty
Disconnect fully in Claude, clear the stale connector, and reconnect so OAuth runs end-to-end. Verify the WaiverTrail user you authenticated with has templates or data in the expected organization. If your team uses multiple orgs, confirm you signed into the right one during OAuth.
Symptom: read works but sends fail
Sends require appropriate scope, template access, quotas, and valid recipient inputs. Read the error literally: quota exceeded, invalid email, or missing template name usually points to configuration—not MCP transport. Compare against in-app sending from the same account to isolate connector versus policy.
Symptom: intermittent disconnects or corporate networks
Some offices block assistant traffic or rewrite TLS. Test from a residential network or mobile hotspot. If it works off-corporate-VPN but not on, involve IT with the hostnames documented in your deployment guide. WAF rules should allow standard OAuth and MCP POST traffic.
When to open a support ticket
Gather timestamp, connector URL (redact secrets), user org, and whether in-app sending still works. Screenshots of the OAuth screen and any opaque error codes speed resolution. Link this article so support knows you already tried revocation and reconnect.
Explore related resources
Preview
integration hub
/integrations/claude
Preview
setup guide
/blog/waivertrail-claude-mcp-send-waivers-seconds
Preview
OAuth, scopes, and data boundaries
/blog/claude-mcp-waiver-security-oauth-scopes
Preview
event waiver workflow
/blog/event-waiver-workflow-claude-mcp
Preview
MCP vs API keys
/blog/waiver-automation-mcp-vs-api-keys
Preview
integrations
/integrations
Frequently asked questions
Does reinstalling Claude fix MCP?
Usually not. Removing and re-adding the connector plus a clean OAuth round trip fixes more than reinstalling the desktop app.
Why did it work yesterday and not today?
Expired sessions, password rotations, org membership changes, and quota resets are common. Start with reconnect and verify account status.
Can I test without production data?
Use a staging tenant or a dedicated test template if your plan supports it. Never run destructive tests against real guest cohorts.
What if two people share one Claude seat?
Avoid it. Shared seats make OAuth attribution ambiguous and complicates revocation.
Is a trailing slash on the MCP URL important?
Use the exact URL your documentation specifies. Wrong paths return 404 or challenge loops.
Where is the business phonebook for integrations?
Start at integrations and your in-app settings; product surfaces change less often than assistant UIs.
Take the next step
Apply these ideas with a modern waiver workflow built for conversion, speed, and compliance.