3,400+ MCP servers ready to use
Vinkius

Bring Pdf Generation
to CrewAI

Learn how to connect Docamatic to CrewAI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Add Elements To PdfGenerate Image From HtmlGenerate Pdf From HtmlGenerate Pdf From TemplateList Available Builtin TemplatesList Generation HistoryMerge Multiple PdfsTake Web Screenshot

What is the Docamatic MCP Server?

Connect your Docamatic account to any AI agent and take full control of your document automation and media production workflows through natural conversation.

What you can do

  • Document Orchestration — Convert raw HTML strings or live website URLs into professional, high-fidelity PDF and image files programmatically
  • Template Intelligence — Create invoices, packing slips, and certificates by injecting dynamic data into predefined built-in templates directly through your agent
  • PDF Manipulation — Draw new elements (text, QR codes, images) onto existing PDF documents or merge multiple files into a single finalized document
  • Visual Intelligence — Capture high-quality full-page screenshots of any live website with automatic JavaScript rendering handling
  • Workflow Monitoring — Access your complete directory of recently generated documents and monitor your production history directly from your agent

How it works

1. Subscribe to this server
2. Retrieve your API Key from your Docamatic account settings
3. Start generating and modifying professional documents from Claude, Cursor, or any MCP client

No more manual document formatting or complex rendering pipelines. Your AI acts as your dedicated document engineer and media production coordinator.

Who is this for?

  • Finance & Admin Teams — instantly generate professional invoices and reports using natural language commands
  • Developers & Ops — automate the creation of technical documentation and capture website snapshots without leaving your terminal
  • Marketing Professionals — scale the production of dynamic certificates and visual collateral through simple AI queries

Built-in capabilities (8)

add_elements_to_pdf

Draw text or images onto an existing PDF

generate_image_from_html

Convert HTML or URL to Image

generate_pdf_from_html

Convert HTML or URL to PDF

generate_pdf_from_template

g. invoice1, packing_slip1) with JSON data. Generate a PDF from a predefined template

list_available_builtin_templates

List common document templates

list_generation_history

List recently generated documents

merge_multiple_pdfs

Combine several PDF files into one

take_web_screenshot

Handles rendering automatically. Capture a full-page website screenshot

Why CrewAI?

When paired with CrewAI, Docamatic becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Docamatic tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Docamatic in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Docamatic and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Docamatic to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Docamatic in CrewAI

The Docamatic MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 8 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Docamatic
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Docamatic for CrewAI

Every tool call from CrewAI to the Docamatic MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I find my Docamatic API Key?

Log in to your account and navigate to the API Key section in your settings to generate or copy your unique access token.

02

Can I use my own custom HTML strings?

Yes! The generate_pdf_from_html and generate_image_from_html tools accept raw HTML strings as source input.

03

Does it support merging existing PDF files?

Absolutely. Use the merge_multiple_pdfs tool and provide an array of public URLs to combine them into a single PDF document.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.