AI Access
AI Access lets you bring DocJacket into Claude, ChatGPT, Codex, Gemini, and any other AI assistant that speaks the Model Context Protocol (MCP). Instead of switching tabs to triage your pipeline, you ask the assistant directly:
"What needs my attention today?" "Which deals are missing inspection reports?" "What's closing this week on the buy side?" "Show me the listing agent on 1234 Main."
The assistant calls into DocJacket, gets a grounded answer from your real book of business, and writes the response in the same chat where the rest of your work already happens.
How it's different from "just another integration"
- Paste-URL-and-go. No API keys, no per-user credentials to manage. You paste
https://mcp.docjacket.com/mcpinto the assistant's connector settings, complete a one-time consent screen, and you're done. - Per-user consent. Each user on your DocJacket account authorizes their own assistant. There's no shared admin token that exposes everyone's data.
- Revocable from settings. DocJacket → Settings → AI Access lists every assistant you've connected. Revoke any of them with one click — the next request from that client returns "unauthorized."
- Audited. Every tool call goes through DocJacket's audit log: which user, which assistant, which tool, what arguments, what result. You can see exactly what an assistant has been doing on your behalf.
- Chat is the approval gate for future writes. Current AI Access is read-first. Draft and action tools are rolling out behind per-tool consent; when enabled, each write executes only after you confirm in the assistant's chat.
What's connected today
The current customer-facing AI Access surface is read-first. Connected assistants can use these DocJacket tools today:
search_transactions— Find deals by address, buyer/seller, or MLS numberget_transaction— Read the full state of one deal, including key dates inlineget_key_dates— Read all deadlines on one transactionget_upcoming_key_dates— Read organization-wide deadlines with a default 14-day horizonget_open_tasks— Read open tasks across the organization or scoped to one transactionget_contacts— Read contacts in your organization by type or querylist_open_contingencies— Read open contingencies on one transactionget_next_required_actions— Answer "what should I do next?" with overdue and upcoming work pre-ranked
Drafting and write tools, such as sending emails, creating tasks, updating key dates, and applying extraction results, are rolling out behind per-tool consent. If your account has access to additional tools, ask the assistant to call mcp_catalog to see the live inventory for your token.
Every connected client and tool call appears in Settings > AI Access and Settings > AI Access > Activity log.
Get started
Pick the assistant you want to connect:
- Connect Claude — Claude.ai, Claude Desktop, Claude Code
- Connect Codex / ChatGPT — Codex CLI, Codex for Work, ChatGPT connectors
- Connect Cowork — Anthropic's team workspace
- Connect Gemini — Google Gemini CLI
Each guide walks you through the connector setup and the OAuth consent flow.
Featured workflow
- Contract Intake — when action tools are enabled, drop a contract PDF in chat, review extracted parties, addresses, key dates, and financials, then confirm before creating the transaction. In the standard read-first setup, use the in-app Upload Documents wizard.
Learn more
- Slash Commands — the 9 pre-built
/docjacket:commands the plugin adds to Cowork + Claude Code - Tool Catalog — the live
mcp_cataloginventory of every tool with description, scope, and example call - Permissions & Scopes — what
read,draft, andactionscover - How the OAuth flow works — Discovery, Dynamic Client Registration, consent, scopes, token rotation, revocation
- DocJacket's AI Features (the assistant inside DocJacket) is a separate thing — AI Access is for assistants outside DocJacket reaching in.
Need help?
If a connection fails, the most common cause is your AI assistant having stale state from a previous failed attempt. Disconnect and reconnect to clear it. If the problem persists, contact support@docjacket.com with the reference ID your assistant shows on the error screen — we can correlate it with our diagnostic logs.