Model Context Protocol
Your AI, working inside Acre Forms.
Connect Claude, ChatGPT, or another AI over MCP. Your assistant can draft transactions, import clients, map form fields, and prep documents — signed in as you, scoped to what your account is allowed to see and change.
What your assistant can do
Read your workspace
Ask about open transactions, sent forms, upcoming closings, or client history. All read-only tools are RLS-scoped to your account.
Draft and update
Create clients from a paste of an email thread, import a CSV, spin up a new transaction, or attach documents — all through natural language.
AI-assisted form mapping
Drop a fillable PDF; your assistant helps map the AcroForm fields to Acre Forms roles. The template lands in Acre Forms for review before it's ever sent.
Guardrails
Humans stay in the loop where it counts
- • Sending forms to a client is not an MCP action. The AI can draft and stage, but a person confirms and hits Send inside Acre Forms.
- • Imported templates are pending review. A Broker/Owner approves suggested field labels before the template is usable.
- • Every action is audited. MCP entries appear in your Integrations page and the brokerage Audit Log tagged as AI-initiated.
- • Same permissions as you. Everything you can do inside Acre Forms, your AI Agent can do.
How we use AI
Transparent by design
- • We use AI to suggest field labels when a new template is imported. Humans review and approve.
- • Client and transaction data is never used to train third-party models. Requests go through providers with no-training terms.
- • Signature capture, PDF hashing, and audit logging are not AI — they are cryptographic and deterministic.
- • You can disconnect any AI assistant at any time from Integrations.