Waiverfile MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Waiverfile MCP or direct API to send waiver forms, fetch signed waivers, check status, and trigger customer notifications through natural language.

Waiverfile logoWaiverfile
Api Key

WaiverFile is an electronic waiver form platform for collecting digital signatures and managing signed waivers online. It streamlines the entire waiver process for businesses that need secure, paperless release forms.

2 Tools

Try Waiverfile now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Waiverfile
Try asking
TOOLS

Supported Tools

Every Waiverfile action and event your agent gets out of the box.

Get Site Details

Retrieve comprehensive configuration and metadata for a WaiverFile site.

Ping Event Service

Ping test for WaiverFile event service connectivity.

SETUP GUIDE

Connect Waiverfile MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["waiverfile"],
  mcp: true,
});
Create a session scoped to Waiverfile and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Show me the public details of our Waiverfile site.",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Waiverfile request
SETUP GUIDE

Connect Waiverfile API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["waiverfile"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Waiverfile
3

Run Waiverfile tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Show me the public details of our Waiverfile site." }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Waiverfile tool calls through the session, and print the final answer

Why Use Composio?

AI Native Waiverfile Integration

  • Supports both Waiverfile MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable tool execution
  • Rich coverage for sending waivers, listing signed forms, and tracking waiver status

Managed Auth

  • Built-in API key management with secure storage and rotation
  • Central place to manage, scope, and revoke Waiverfile access
  • Per user and per environment credentials instead of hard-coded keys

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve reliability over time
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Waiverfile
  • Scoped, least privilege access to Waiverfile resources
  • Full audit trail of agent actions to support review and compliance

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

Yes, Waiverfile requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Waiverfile connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Waiverfile account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Waiverfile actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Waiverfile at any time.

When you connect a Waiverfile account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Waiverfile as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Waiverfile. If Waiverfile lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Waiverfile at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Waiverfile connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Waiverfile rejects the old key. Create a new key in Waiverfile and reconnect the account from the Composio dashboard or by asking your agent to reconnect Waiverfile. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Waiverfile use. Paid plans add higher limits and team features. Your Waiverfile plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Waiverfile accounts).

With Composio, you connect Waiverfile once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Waiverfile.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Waiverfile tool your agent needs.Free to start.

Start building