# Futuras.ai: E-Signature by Futuras

> An e-signature service that AI assistants use through a connector. A person asks their assistant to
> get a PDF signed; the assistant prepares the request, the person approves it, the signers sign by
> private link, and the signed file and its record come back to the conversation.

Status: early access, by invitation.

## Connect

- Remote MCP server (streamable HTTP, OAuth 2.1, sign-in by email code): https://mcp.futuras.ai/mcp
- Claude Code: `claude mcp add --transport http --scope user futuras-sign https://mcp.futuras.ai/mcp`, then `/mcp` to sign in.
- Claude: Settings, Connectors, Add custom connector, paste the address.

## Flow

1. create_upload: a one-time link for a local PDF (skip for an HTTPS URL or a file under 2 MB).
2. prepare_envelope: a draft with signers and suggested signature, initial and date fields. Nothing is sent.
3. Show the person the review PDF. update_envelope changes it; preview_envelope re-reads it.
4. send_envelope: only when the person says to send.
5. status: who has opened and signed. invite_remaining_signers reminds. void_envelope cancels.
6. get_signed_copy and get_certificate when complete.

## Limits

PDF only, up to 25 MB and 60 pages, up to ten people per request. Not for wills, powers of attorney
or other documents the law does not allow to be signed electronically. Never sign on a signer's behalf.

## Pages

- [How it works](https://futuras.ai/docs)
- [Connect](https://futuras.ai/connect)
- [Security](https://futuras.ai/security)
- [Verify a signed document](https://futuras.ai/verify)