Complete MCP server exposing 14 doqs.dev | PDF filling API operations to AI agents.
This workflow converts the doqs.dev | PDF filling API into an MCP-compatible interface for AI agents.
• MCP Trigger: Serves as your server endpoint for AI agent requests
• HTTP Request Nodes: Handle API calls to https://api.doqs.dev/v1
• AI Expressions: Automatically populate parameters via $fromAI()
placeholders
• Native Integration: Returns responses directly to the AI agent
• GET /designer/templates/: List Templates
• POST /designer/templates/: Create Template
• POST /designer/templates/preview: Preview
• DELETE /designer/templates/{id}: Delete
• GET /designer/templates/{id}: List Templates
• PUT /designer/templates/{id}: Update Template
• POST /designer/templates/{id}/generate: Generate Pdf
• GET /templates: List
• POST /templates: Create
• DELETE /templates/{id}: Delete
• GET /templates/{id}: Get Template
• PUT /templates/{id}: Update
• GET /templates/{id}/file: Get File
• POST /templates/{id}/fill: Fill
Parameter Handling: AI agents automatically provide values for:
• Path parameters and identifiers
• Query parameters and filters
• Request body data
• Headers and authentication
Response Format: Native doqs.dev | PDF filling API responses with full data structure
Error Handling: Built-in n8n HTTP request error management
Connect this MCP server to any AI agent or workflow:
• Claude Desktop: Add MCP server URL to configuration
• Cursor: Add MCP server SSE URL to configuration
• Custom AI Apps: Use MCP URL as tool endpoint
• API Integration: Direct HTTP calls to MCP endpoints
• Zero Setup: No parameter mapping or configuration needed
• AI-Ready: Built-in $fromAI()
expressions for all parameters
• Production Ready: Native n8n HTTP request handling and logging
• Extensible: Easily modify or add custom logic
🆓 Free for community use! Ready to deploy in under 2 minutes.