DocJacket — Transaction Coordination plugin for Claude
Connect DocJacket transactions, tasks, deadlines, contacts, and document checklists to Claude. Triage your pipeline, draft and send follow-up emails from your connected Gmail/Outlook, classify inbound attachments against the right deal — all from inside Claude.
Works with: Claude.ai (sidebar) · Cowork · Claude Code · Claude Desktop
What you get
- Full read + send tool suite via the DocJacket MCP server at
https://mcp.docjacket.com/mcp. Call mcp_catalog after install for the live inventory + per-tool gotchas and example calls.
mcp_health_check — first call when integrating; verifies auth, scopes, and DB reachability before you start a workflow.- 8 skills ship with this plugin:
daily-triage, email-triage, closing-prep, follow-up-drafting, document-filing, contact-management, execution-workflow, tc-context. The agent picks them automatically based on what you ask.
- 9 slash commands (Cowork + Claude Code):
/docjacket:morning-briefing, /docjacket:whats-next, /docjacket:email-triage, /docjacket:doc-check, /docjacket:weekly-report, /docjacket:share-portal, /docjacket:intake-contract, /docjacket:send-template, /docjacket:check-submissions. See Slash Commands reference for what each one does.
- Status Reporter sub-agent (Cowork) — read-only weekly briefing across every active deal.
Three scope tiers — Read (search, summarize), Draft (compose without sending), Actions (send emails, create tasks, update dates). You authorize once at OAuth consent; the chat is the per-call approval gate.
Tool catalog
Selected highlights below. For the live and complete list with per-tool gotchas, pairing hints, and example calls, run mcp_catalog after install — the server returns its own enumeration so this README never drifts.
| Tool | Purpose |
|---|
mcp_health_check | Verify auth, scopes, and DB reachability. Run this first when integrating. |
mcp_catalog | Enriched list of every tool you can call — gotchas, pairings, examples. |
search_transactions | Search by address, party name, MLS, status |
get_transaction | Full state of one deal including joined key dates + parties |
get_key_dates | Key Dates for one transaction |
get_upcoming_key_dates | Org-wide upcoming deadlines, default 14-day horizon |
get_next_required_actions | Bundled judgment — overdue + upcoming, pre-ranked with rationales |
get_missing_documents | Universal-baseline missing-doc detection for purchase deals |
find_transaction_by_property | Fuzzy address-to-deal matching with confidence scores |
list_active_transactions | Inbox-workflow shortcut — every active deal, optional party / key-date expansion |
search_contacts / get_contact | Contact lookup by name/email/phone/company |
list_email_templates / get_email_template / render_email_template | Templated email composition |
send_client_update / send_agent_followup / send_document_request / send_email_to_agent | Direct execution from your connected Gmail/Outlook |
create_tasks / update_key_date / complete_task / save_status_summary | Direct execution against DocJacket |
Install
No bearer tokens. No manual config. Paste the server URL, click Allow on the consent screen, you're done. OAuth 2.1 + Dynamic Client Registration end-to-end.
Prerequisites
A DocJacket account on the Pro plan. Connecting is free; loading tools requires Pro.
Claude.ai (web sidebar)
- Settings → Connectors → + Add custom connector
- Paste:
https://mcp.docjacket.com/mcp
- Click Continue, then Allow on the DocJacket consent screen
The tool list loads. Run mcp_health_check once to confirm scopes; then mcp_catalog for the full inventory.
Claude Desktop
Same flow as Claude.ai:
- Settings → Connectors → + Add custom connector
- Paste:
https://mcp.docjacket.com/mcp
- Complete the OAuth consent screen
Claude Code / Cowork (plugin)
/plugin marketplace add docjacket-inc/claude-plugin
/plugin install docjacket
On first tool call, your browser opens to complete OAuth consent. Access + refresh tokens are stored in your local keychain — no secrets in config files.
Claude Desktop (manual config, advanced)
If you prefer editing ~/Library/Application Support/Claude/claude_desktop_config.json directly:
