# Accord

> Accord is a free, bilingual service that lets a person or an authorized agent prepare a non-fillable PDF and send it for acceptance, approval, acknowledgement, or signature. Durable files stay in the connected Google Drive and email invitations are sent from the connected Gmail account.

## Agent start here

- **MCP FIRST:** if your runtime supports MCP, use Accord through MCP. Drive the human Web UI only as a fallback.
- Read the complete, executable setup and safety guide: https://accord.paz.team/agent-setup/prompt.md
- Connect an OAuth-capable MCP client to: https://accord.paz.team/api/mcp
- Do not ask for a Google password, Google token, Gmail contents, or broad Drive access.
- Do not claim that Accord is connected until MCP `initialize` succeeds and `tools/list` returns the Accord tools.
- Then call `get_accord_account_status`; never guess which Google or Gmail account is active.

## Choose the identity context

- An autonomous agent with its own Google identity can sign in to Accord with that identity and authorize its own MCP client in the browser.
- An agent acting for a person or organization must use that owner's Accord authorization. It never receives the owner's Google token.
- An unauthenticated visitor can read this guide and verify an Accord certificate, but cannot access private files or perform owner actions.

## What the Accord MCP can do

- Receive one explicitly supplied PDF through a bounded upload capability.
- If the owner supplies a DOCX, convert it locally to PDF with a trusted renderer, visually verify every converted page, then use the existing PDF workflow. Never upload DOCX bytes to the PDF capability. The human Web app can also convert a DOCX privately inside the connected Drive.
- Report the exact connected owner and keep three Google states separate: connection, granted Drive/Gmail permissions, and the optional operational test. Use the returned capabilities as the action-readiness source; an operational test that has not run is not a blocker by itself.
- Analyze the PDF, render numbered page previews, and suggest fields.
- Add, move, resize, rename, retype, or remove fields against a revisioned draft.
- List the connected owner's reusable Accord forms.
- Send a confirmed PDF or saved form to a confirmed signer through the owner's Gmail.
- Create a confirmed temporary Accord link without sending email.
- Read status, cancel an unfinished request after confirmation, or retry a recoverable request.

## What the Accord MCP cannot do

- Read or search Gmail.
- Browse arbitrary Drive files or access another Accord account.
- Receive a Google access token or make a Drive file public.
- Send a real invitation or create an active link without the required permissions and explicit confirmation of the action, delivery mode, intended signer when known, and final revision.
- Guarantee a person's real identity, legal authority, email delivery, or universal legal validity.

## Required workflow for a new PDF

1. Preserve the exact raw PDF bytes, byte length, and lowercase SHA-256.
2. Begin the private preparation and upload only those declared bytes.
3. Analyze the draft and preview every page, including pages with no suggested field.
4. Correct every required field and stop on `missingSignature`, `needsReview`, or `truncated`.
5. Show the owner the file, requested action, delivery mode, intended signer when known, language, expiry, message, field summary, and exact latest revision.
6. Ask for explicit confirmation, then send by Gmail or create the link for exactly that confirmed revision with a stable idempotency key.
7. Report the request identifier and actual Accord status without inventing delivery or completion.

For a DOCX, first create a local PDF without changing the document content, inspect every rendered page for clipping or layout drift, then begin at step 1 with the exact converted PDF bytes. Personal fill-and-sign without email or certificate is currently a human Web flow; do not claim the MCP completed that interactive signature.

## Public links

- Human web app: https://accord.paz.team
- Agent setup skill: https://accord.paz.team/agent-setup/prompt.md
- MCP server: https://accord.paz.team/api/mcp
- Privacy: https://accord.paz.team/privacy
- Terms: https://accord.paz.team/terms
- Certificate verification: https://accord.paz.team/verify

---

## Français

Accord est une capacité MCP gratuite pour préparer un PDF non remplissable et le faire accepter, approuver, reconnaître ou signer. Un agent autonome possédant sa propre identité Google peut ouvrir son propre compte Accord. Un agent qui représente une personne ou une organisation utilise plutôt l'autorisation Accord de ce propriétaire. Dans les deux cas, l'agent ne reçoit jamais le jeton Google.

**MCP D’ABORD :** lisez https://accord.paz.team/agent-setup/prompt.md, connectez le client MCP à https://accord.paz.team/api/mcp, vérifiez `initialize` et `tools/list`, puis appelez `get_accord_account_status`. Distinguez toujours la connexion, les permissions accordées et le test opérationnel facultatif; utilisez les capacités retournées pour décider ce qui peut être tenté. Un test non exécuté ne bloque rien à lui seul. Respectez l'aperçu de chaque page et la confirmation explicite avant tout courriel ou lien actif. Le MCP ne peut ni lire Gmail, ni parcourir librement Drive, ni accéder à un autre compte.

Si le propriétaire fournit un DOCX, convertissez-le localement en PDF avec un moteur fiable, vérifiez visuellement chaque page convertie, puis utilisez le parcours PDF existant. Ne téléversez jamais les octets DOCX dans la capacité PDF. L’interface Web humaine accepte aussi les DOCX et les convertit dans le Drive connecté. Le remplissage et la signature personnels sans courriel ni certificat demeurent un parcours Web interactif; ne prétendez pas que le MCP a réalisé cette signature humaine.