CraftMyPDF MCP integration for AI agents.
Connect AI agents to CraftMyPDF through 4 structured actions, including get account info, create pdf, and get template. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the CraftMyPDF integration exposes
The CraftMyPDF Agent App exposes 4 provider-backed actions for design & media and productivity work. Its current contract lets an authorized agent get the current craftmypdf account details resolved by the provided api key, generate a pdf from a craftmypdf template and return the hosted file url plus transaction metadata, and get the raw craftmypdf template body and sample json for one template id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected CraftMyPDF account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real CraftMyPDF capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_infoREADGet the current CraftMyPDF account details resolved by the provided API key.
create_pdfWRITEGenerate a PDF from a CraftMyPDF template and return the hosted file URL plus transaction metadata.
INPUTS: templateId / data / loadDataFrom / version / expiration
get_templateREADGet the raw CraftMyPDF template body and sample JSON for one template ID.
INPUTS: templateId / version
list_templatesREADList CraftMyPDF templates with optional pagination and group-name filtering.
INPUTS: limit / offset / groupName
INPUT CONTRACTS
Know what the action needs before it runs.
create_pdf
templateIdREQUIRED- The CraftMyPDF template_id value.
dataREQUIRED- The template data payload. CraftMyPDF accepts a JSON string or JSON object.
loadDataFromOPTIONAL- An optional external URL for loading template data.
versionOPTIONAL- The optional template version string. Omit it to use the latest version.
expirationOPTIONAL- The file URL expiration time in minutes.
get_template
templateIdREQUIRED- The template identifier to retrieve.
versionOPTIONAL- The optional template version string. Omit it to retrieve the latest version.
list_templates
limitOPTIONAL- The maximum number of templates to return.
offsetOPTIONAL- The number of templates to skip before returning results.
groupNameOPTIONAL- Filter templates by CraftMyPDF group_name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Info
Get the current CraftMyPDF account details resolved by the provided API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_infoControl Create Pdf
Generate a PDF from a CraftMyPDF template and return the hosted file URL plus transaction metadata. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_pdfVerify with Get Template
Get the raw CraftMyPDF template body and sample JSON for one template ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_templateSAFETY BOUNDARY
Operate CraftMyPDF with explicit limits
- Authorize CraftMyPDF with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in CraftMyPDF rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the CraftMyPDF task completed successfully.
CONNECTION MODEL
API key
CraftMyPDF API key sent with the X-API-KEY header. Get or reset it from the CraftMyPDF web console under API Integration, as described in the official docs: https://craftmypdf.com/docs/index.html.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by CraftMyPDF.