signit
Connect an agent

Connect Claude.ai

Attach a PDF in Claude chat and request signatures with Signit.

Available now

Connect Signit to Claude.ai

Claude can create and send from a chat attachment when its computing environment can reach Signit. Live client verification of the new attachment flow is pending.

  1. In Signit, select Connect to Claude, add Signit, then Connect and approve creation and sending access. The canonical endpoint is https://app.sign-it.ro/mcp.
  2. Enable Code execution and file creation and network access to app.sign-it.ro; MCP connectivity alone does not enable attachment transfer.
  3. Attach a PDF up to 3 MiB in Claude chat and ask Signit to send it to the named Signers with their email addresses. No separate Signit upload is required.
  4. Reconnect existing grants to approve sending permissions. Hosted private PDF review remains limited to 3 MiB and signing requires explicit consent.
Claude custom connector documentation

Add, connect, then attach

In Signit, open Agent connection → Connect to Claude. Add Signit in Claude, select Connect, sign in to Signit, and approve creation and sending access. You can also add https://app.sign-it.ro/mcp as a custom connector from Claude's Customize → Connectors. Reconnect existing grants to approve the added scope.

Enable Signit in a conversation, attach one PDF, and ask:

I want this attached PDF signed by Alice (alice@example.com), Bob (bob@example.com), and Carol (carol@example.com). Send it through Signit, with parallel signing and English invitations.

Claude reads the original attachment in its computing environment, transfers those exact bytes to Signit, then creates and sends the Envelope. No separate upload in Signit is required. If you ask only to prepare a draft, sending waits for your instruction. Creation accepts autoDetectSignatureFields (default true): Signit reads the whole PDF in the background and places each Signer's fields at their signature blocks; false skips the analysis and puts every Signer on an added signature page. While the PDF is still being read, sending waits briefly and then returns a placement-pending result with retryAfterSeconds; Claude retries the same send request.

Required Claude capabilities

Enable Code execution and file creation and allow network access to app.sign-it.ro. Connecting the MCP tools does not itself allow outbound requests from Claude's computing environment. Team/Enterprise owners can add Signit's domain under Organization settings → Capabilities. Package-manager-only network access is insufficient. Available controls differ by plan; if your workspace cannot permit Signit's domain, the attachment transfer cannot run. See Claude's file and network settings.

In Claude Code the sandbox pre-allows no domain: the first connection asks for your approval, and "Yes, and don't ask again" keeps it for later sessions. You can pre-allow it by adding app.sign-it.ro to sandbox.network.allowedDomains in .claude/settings.json. Some environments instead use a managed allowlist you cannot change, including the Claude Code web sandbox; there the attachment transfer cannot run at all. Upload the PDF in Signit and ask the agent only to send the draft. A transfer stopped by the network creates no Envelope, and the upload instructions return the exact domain to allow.

Limits and retry behavior

Chat attachment transfers support PDFs up to 3 MiB and 200 pages. The original bytes must be preserved. Claude must not reconstruct a contract from its extracted text. An expired upload authorization can be renewed by retrying the same creation request; the same operation must not create another Envelope.

The connector also lists your pending signatures, returns an authorized private PDF resource for review together with every field prepared for you and its fieldSetDigest, and signs only your own assignment with explicit consent; signing must pass that digest and applies the adopted name to every field in the set. Hosted review remains capped at 3 MiB. Read the complete document before signing; if the client cannot read it, finish signing in Signit.

The new attachment flow still requires live verification in Claude.ai with code execution and the actual account's network settings enabled.

Hosted operator requirements

Production is the canonical HTTPS origin https://app.sign-it.ro. Set BETTER_AUTH_URL=https://app.sign-it.ro; the button intentionally stays hidden when that value is not a canonical public HTTPS origin.

Database migrations run from main through the repository's Database migrations workflow. It runs wrangler d1 migrations apply signit --remote against the production D1 database, authenticated by the CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID secrets. Do not put either secret in the docs, a prompt, or a client-side setting.

See the official Claude custom-connector documentation.

On this page