Docnify

@Docnify show me all documents waiting for signatures from external partners in the last 30 days

Found 7 documents pending external signatures: 1. **Vendor Agreement - Acme Corp** (ID: doc_8x9k2) • Sent Jan 15 • Awaiting: Sarah Chen (sarah@acme.com) 2. **NDA - Beta Testers** (ID: doc_7m3p1) • Sent Jan 12 • Awaiting: 3 recipients 3. **Consulting Contract - J. Martinez** (ID: doc_6n4r8) • Sent Jan 8 • Awaiting: Jorge Martinez 4. **Partnership MOU - TechFlow** (ID: doc_5k2w9) • Sent Jan 6 • Awaiting: Legal team review 5-7. [Additional documents listed] This is an illustrative example showing typical document metadata returned by Docnify's List Documents tool.

This example demonstrates read-only document querying. The actual API returns structured metadata (status, recipient info, timestamps) that the AI summarizes into readable format. Requires valid API key with read permissions. Results depend on your account's document history and current signing workflows.

@Docnify create a new W-9 request for contractor Emma Rodriguez at emma@freelance.dev, make her the only signer with email authentication required

Created document **W-9 Tax Form Request** (ID: doc_9t5k3) and added Emma Rodriguez as recipient. **Configuration applied:** • Recipient: emma@freelance.dev • Role: Signer (signing order: 1) • Authentication: Email verification required before access • Status: Draft (ready to add fields or send) Next steps: You can now add signature fields to the document using Create Document Fields, or send it immediately if the template already contains required fields. This example shows the typical flow after using Add Document Recipient.

This example chains document creation with recipient setup, demonstrating write operations. In practice, you'd first create or select a document (possibly from a template), then add recipients with specific authentication requirements. Changes are immediate and irreversible once sent, so verify recipient details carefully. Requires API key with document creation permissions.

@Docnify review all unsigned NDAs from Q4 2024 and draft a follow-up email for recipients who haven't signed after 2 weeks

Analyzed 12 NDAs from Q4 2024. Found 4 documents unsigned after 14+ days: **Overdue signatures:** • **NDA - Vendor Discovery** (doc_4k8m2) • Sent Nov 18 • Awaiting: Mike Thompson (mike@vendor.com) • 58 days overdue • **Mutual NDA - Partner Talks** (doc_3n7p1) • Sent Dec 3 • Awaiting: Legal contact • 43 days overdue • [2 additional documents] **Suggested follow-up email:** *Subject: Signature Reminder: [Document Name]* Hi [Recipient Name], We sent you [Document Name] on [Date] and haven't received your signature yet. Could you review and sign by [Date + 7 days]? Reply if you have questions or need the document resent. This illustrative example shows how the AI synthesizes Docnify data into actionable insights.

This example showcases AI reasoning layered on top of Docnify's document data. The MCP provides raw document status; the AI identifies patterns (overdue items) and generates contextual output (draft email). Useful for workflow management, but remember the AI doesn't automatically send reminders—you control all outbound communication. Requires read access to historical documents.

When Docnify beats manual email for proposal signatures

A 6-person sales team closing deals across three time zones needs to route NDAs and SOWs without Slack threads full of 'did they sign yet?' questions. Docnify wins here because the MCP exposes recipient management and document status in the same context where the team is already drafting deal notes. One person creates the contract fields, adds the three signers with authentication requirements, and the whole sequence lives in a shared workspace thread instead of scattered across inboxes. The trade-off: if your contracts need complex conditional logic or multi-party negotiation rounds, you'll hit the MCP's 13-tool ceiling fast. But for straightforward signature collection on 10-20 deals a month, this keeps the entire contract lifecycle visible to the team without anyone logging into a separate portal.

Use Docnify MCP when template reuse matters more than custom workflows

A 3-person ops team onboards 4-6 new hires per quarter and needs offer letters, I-9s, and benefits forms signed in a specific order. The MCP's template fetching and field creation tools let them build a reusable onboarding checklist once, then clone it per candidate without re-entering signer details or field positions. The signing-order parameter ensures the background check clears before the equity grant goes out. This works well up to about 15 hires per quarter—beyond that, you want dedicated onboarding automation, not an MCP bolted onto a chat workspace. The buying call: if your hiring is lumpy and you'd rather script the packet assembly in a shared AI context than maintain a separate onboarding app, Docnify's API-key auth and 13 tools cover the essentials without forcing you into a heavier platform.

When document listing beats folder archaeology at month-end

A 2-person finance team closes books monthly and needs to confirm which vendor agreements were executed in the prior 30 days. The List Documents tool filters by date range and status, so they can pull a snapshot of signed contracts without digging through email or a filing cabinet. The Get Document call surfaces metadata like signing timestamps and recipient lists, which feeds directly into their accrual spreadsheet. This scenario is borderline: if you're tracking hundreds of vendor agreements or need audit trails with version history, the MCP's 13 tools won't replace a proper contract lifecycle system. But for a small team doing quarterly or monthly spot-checks on 20-40 agreements, having document status queryable in the same workspace where they're reconciling invoices saves the context-switch tax. Use this if your audit frequency is low and your document volume fits in a single API call.