Agents and automation
Connect the PDFDesignAPI MCP server
Connect an MCP client to manage templates and generate PDFs with a team-scoped API key.
Reviewed 2026-08-05 · PDFDesignAPI Engineering
Endpoint: https://pdfdesignapi.com/api/mcp
OpenCode
Add a project-level remote server to opencode.json and keep the token in your environment.
- Set PDFDESIGNAPI_API_KEY in the shell that launches OpenCode.
- Merge this entry into opencode.json in the project root.
- Restart OpenCode and verify that the pdfdesignapi tools are available.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pdfdesignapi": {
"type": "remote",
"url": "https://pdfdesignapi.com/api/mcp",
"headers": {
"Authorization": "Bearer {env:PDFDESIGNAPI_API_KEY}"
}
}
}
}Create an API key
Open the API integration page in PDFDesignAPI and create a team API key. The MCP server uses the same team scope as the API.
Store the key in a protected environment variable named PDFDESIGNAPI_API_KEY. Never commit it to source control or paste it into prompts.
export PDFDESIGNAPI_API_KEY="YOUR_API_KEY"Available operations
The server can list and inspect templates, create templates, replace a complete editable design, archive templates, restore archived templates, and generate PDF resources.
Deletion is deliberately reversible. The delete_template tool sets archived_at; restore_template returns the same UUID, versions, and design to the active interface.
Embedded skill
The server sends operating instructions during MCP initialization and exposes the pdfdesignapi-integration prompt and pdfdesignapi://skill resource.
Clients should follow that guidance: discover before editing, preserve complete designs, use schema-matching data, and prefer production aliases or explicit versions for stable integrations.