Documint
Documint is a document generation platform that allows you to create dynamic documents from templates.
Verdict
Common use cases
- Generate invoices from Slack threads
- Turn meeting notes into client proposals
- Create signed contracts from form data
- Produce compliance reports on demand
- Issue certificates after training sessions
Integration
- Vendor
- Documint
- Category
- docs
- Auth
- API_KEY
- Tools
- 5
- Composio slug
documint
Tools
- Delete Templatedestructive
Tool to permanently delete a single template by its id. use when you need to remove an outdated or unused template; ensure the template id is correct before calling.
- Get Template
Tool to retrieve a single template by its id. use when you need to fetch details of a specific template before generating documents.
- List Documents
Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.
- List Templates
Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.
- Update Template
Tool to update a single template by its id. use when you need to modify an existing template's settings or layout after fetching its current details.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations page. 2. Find Documint in the catalog and click Connect. 3. Log into your Documint account at documint.me, go to Settings > API Keys, and generate a new key with read/write permissions for templates and documents. 4. Paste the API key into Switchy's connection dialog and click Authorize. 5. Return to any Space and type '@Documint list my templates' to confirm the connection works — you should see a list of templates from your Documint account. 6. To generate a document, @mention Documint again and ask it to fetch a template by ID, then provide the data you want merged into that template.
What teammates see: by default, memories from Documint are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Templates
@Documint list all templates in my account and show me their names and IDs.Open in a Space →
Fetch Template Details
@Documint get the template with ID abc123 and show me what fields it expects.Open in a Space →
Generate Invoice
@Documint use template xyz789 to generate an invoice for Acme Corp with line items: consulting $5000, hosting $200.Open in a Space →
Update Template Settings
@Documint update template def456 to change the footer text to 'Confidential – Do Not Distribute'.Open in a Space →
Delete Unused Template
@Documint delete the template with ID old999 because we've replaced it with a new version.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Documint list all templates in my account and show me which ones haven't been used in the last 30 days
I've retrieved your Documint templates. You have 12 templates total. Based on the metadata, 4 templates appear unused recently: 'Q3 Invoice Template' (last modified 47 days ago), 'Legacy Contract v2' (last modified 89 days ago), 'Old Onboarding Packet' (last modified 112 days ago), and 'Test Template Draft' (created 6 months ago, never finalized). The other 8 templates show recent modification dates within the past 3 weeks, suggesting active use.
This example shows the MCP's read capability for template discovery. The List Templates tool returns metadata but doesn't track actual document generation events, so 'last modified' is a proxy for usage. You'll need a valid API key with read permissions on templates.
@Documint update the 'Client Proposal Template' to change the footer text to include our new address and phone number
I've updated the 'Client Proposal Template' (ID: tmpl_8x9k2m). The footer now displays: '123 Market Street, San Francisco, CA 94103 | (415) 555-0199'. The template version incremented to v4 and is immediately available for new document generation. Existing documents generated from earlier versions remain unchanged.
This demonstrates the MCP's write capability for template modification. The Update Template tool requires the exact template ID (fetch it first with Get Template or List Templates). Changes apply only to future document generations—previously rendered documents are immutable snapshots.
@Documint review all my templates and draft a short audit report identifying which ones have inconsistent branding or outdated legal disclaimers
I've analyzed your 12 Documint templates. Branding inconsistencies: 5 templates use the old logo file 'logo_2022.png' instead of 'logo_2024.png'; 3 templates have font mismatches (mixing Arial and Helvetica in headers). Legal disclaimer concerns: 'Service Agreement Template' and 'Contractor NDA' both reference a 2021 privacy policy URL that may be outdated. The 'Employee Handbook Template' footer still lists your previous business entity name. I recommend updating these 8 templates for brand and compliance alignment.
This example pairs the MCP's List Templates and Get Template tools with the AI's reasoning to perform cross-template analysis. The AI can spot patterns humans miss, but it can't verify legal compliance—always have counsel review substantive contract language before acting on these suggestions.
Use-case deep-dives
When Documint beats manual contract assembly at 10+ deals/month
A 6-person sales team closing 15 deals a month needs NDAs, MSAs, and SOWs generated from Salesforce data without copy-paste errors. Documint wins here because the List Templates and Get Template tools let your AI pull the right contract shell, then generate the PDF with merged fields in one pass. The threshold: if you're under 10 deals a month, the API key setup and template maintenance overhead probably isn't worth it—just use a shared Google Doc. Above that volume, the time saved on manual merges and the reduction in typo risk justify the integration. If your contracts need complex conditional logic or multi-party routing, you'll still need DocuSign or PandaDoc on top of this.
Documint for repeatable employee document workflows
A 3-person HR team onboarding 8-12 hires per quarter needs offer letters, benefits summaries, and I-9 instructions generated from BambooHR or Rippling. Documint is the right call if your packets are template-driven and data comes from a single HRIS—the List Documents tool lets your AI confirm what's already been sent, and Update Template keeps the benefits language current without re-uploading PDFs. The trade-off: if your onboarding docs need e-signatures or audit trails, Documint only handles generation; you'll route the output to DocuSign. If your hire volume is under 6 per quarter, the manual effort is low enough that this MCP adds more config burden than it saves. At 8+ hires, the consistency gain and time saved make it a clear win.
When Documint handles monthly reporting at 20+ client scale
A 10-person marketing agency sends 25 clients a monthly performance report with charts, commentary, and next-month recommendations. Documint works if your reports follow a fixed layout and pull data from Google Analytics, HubSpot, or a BI tool—the Get Template and List Templates tools let your AI pick the right report shell per client tier, then merge the numbers and narrative in one shot. The boundary: if your reports are highly custom or need interactive elements, Documint's PDF output won't cut it; you'd need Notion or Coda instead. If you're under 15 clients, the template setup and API key management overhead outweighs the time saved. At 20+ clients, the reduction in manual formatting and the ability to batch-generate reports in Slack makes this MCP a strong fit.
Frequently asked
What does the Documint MCP do in Switchy?
It connects your Documint account so AI agents can list, fetch, update, and delete document templates, plus retrieve generated documents. Useful when you need agents to automate PDF or document generation workflows without leaving the chat. The MCP doesn't create new templates from scratch—only manages existing ones.
Do I need admin access to connect Documint?
You need a Documint API key with read-write permissions on templates and documents. Any account holder can generate one from the Documint dashboard. If your Documint workspace has role-based access, make sure the key's owner can delete and update templates, not just read them.
Can the Documint MCP create new templates or just edit existing ones?
It can only update or delete templates that already exist in your Documint account. There's no tool to create a template from scratch via the MCP. If you need a new template, build it in Documint's editor first, then the agent can modify or generate documents from it.
Why use this instead of calling Documint's API directly?
The MCP wraps Documint's REST API so agents can manage templates in natural language without you writing code. If your team already has a script that calls Documint, keep it. If you want agents to trigger document generation mid-conversation or update templates on the fly, the MCP is faster.
Who on the team should connect the Documint integration?
Whoever owns the Documint account and can generate an API key. Typically that's someone on ops, marketing, or finance who manages document templates. Once connected in Switchy, any team member can ask agents to list or update templates—the key's permissions apply to everyone.