Connect AI Tools

Waafir exposes part of the platform as a set of Model Context Protocol (MCP) servers, so an AI client you already use — Claude Desktop, Cursor, or any other MCP-compatible tool — can work with your data room directly. Where the AI features section describes the AI workforce inside Waafir, this section is about connecting your own AI client to Waafir.

What is MCP, here?

The Model Context Protocol is an open standard that lets an AI client call tools exposed by a server. Waafir runs four such servers, each one a focused surface:

• waafir-redact — redact sensitive content, either inline in a block of text or across a whole document in a data room.
• waafir-translate — translate between languages, either a snippet of text inline or a whole document in a data room.
• waafir-dataroom — read and manage your data rooms: list and search files, manage folders, handle the file lifecycle and its versions, read a document's extracted text, follow investor Q&A, and control access.
• waafir-esign — create e-signature envelopes, collect legally-valid AES signatures, and download signed documents. A paid offering with a monthly signature quota — see the waafir-esign reference.

Each server is reachable over plain HTTP (MCP's Streamable HTTP transport), so any standards-compliant client can connect. The redaction and translation servers are positioned as experimental; the data room server is the stable API surface of this release.

The shape of connecting

Getting an AI client working with Waafir is always the same three steps:

1. Authenticate — issue a Personal Access Token (PAT) from Add-ons → Connect. Every request to a Waafir MCP server is authenticated with a PAT — there is no anonymous access, and a logged-in browser session is not accepted on this surface.
2. Connect — add each server you want to your client's MCP configuration, pointing it at the correct per-server URL and supplying your PAT as a bearer token.
3. Call tools — once connected, your client lists the server's tools and calls them on your behalf. What a token can do is bounded by its scope (read / write / admin) and, optionally, by the specific data rooms it is restricted to.

In this section

• Personal Access Tokens — where to issue a PAT, what the scopes mean, how to limit it to specific data rooms, expiry, and revocation.
• Setup — the per-server connection URLs and ready-to-paste configuration for Claude Desktop and Cursor, plus the errors you may hit and what they mean.
• waafir-redact reference — all three redaction tools: redact_text, redact_file and redact_file_status.
• waafir-translate reference — all three translation tools: translate_text, translate_file and translate_file_status.
• waafir-dataroom reference — all thirty data room tools, grouped by what they do.
• waafir-esign reference — all nine e-signature tools, the paid-access model, and the monthly signature quota.

A token only ever carries the authority of the person who issued it: an MCP tool can never do something through Waafir that the token's owner could not do in the product itself. Start with Personal Access Tokens.