doqs.dev PDF Form Filling API as an MCP Server

## 🛠️ doqs.dev | PDF filling MCP Server ✅ 14 operations ### 🔧 How it Works 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 ### 📋 Available Operations (14 endpoints) Designer (7 operations) list, create, preview, delete, update, generate Templates (7 operations) list, create, delete, get, update, fill ### ⚙️ Setup Instructions 1. Import Workflow: Load this workflow into your n8n instance 2. Configure Authentication: Set up apiKey credentials - Type: API Key in header - Key name: x-api-key 3. Activate Workflow: Enable the workflow to start the MCP server 4. Get MCP URL: Copy the webhook URL from the MCP trigger 5. Connect AI Agent: Use the MCP URL in your AI agent configuration ### 💡 Usage Notes • Parameters are auto-populated by AI using $fromAI() expressions • With 14 API endpoints available as tools • Responses maintain original API structure ### 🛠️ Customization • Add data transformation nodes if needed • Implement custom error handling • Add logging or monitoring nodes • Modify parameter defaults in any HTTP request node as needed ### 💬 Need Help? Check the n8n documentation or ping me on discord for MCP integration guidance or customizations.