Encodian MCP integration for AI agents.
Connect AI agents to Encodian through 5 structured actions, including get pdf text layer, compress pdf, and extract pdf pages. Review authentication, inputs…
- ACTION CONTRACTS
- 5
- 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 Encodian integration exposes
The Encodian Agent App exposes 5 provider-backed actions for productivity and design & media work. Its current contract lets an authorized agent extract the text layer from one pdf document with optional page-range and encoding controls, compress one pdf document with encodian and return the optimized pdf file as base64 content, and extract selected pages from one pdf document and return the resulting pdf file as base64 content. 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 Encodian account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Encodian capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_pdf_text_layerREADExtract the text layer from one PDF document with optional page-range and encoding controls.
INPUTS: fileName / fileContent / startPage / endPage / textEncodingType
compress_pdfREVIEWCompress one PDF document with Encodian and return the optimized PDF file as base64 content.
INPUTS: fileContent / compressImages / imageQuality / maxResolution / resizeImages
extract_pdf_pagesREVIEWExtract selected pages from one PDF document and return the resulting PDF file as base64 content.
INPUTS: fileContent / startPage / endPage / pageNumbers
secure_pdf_documentREVIEWEncrypt one PDF document with optional open and edit passwords, then return the protected PDF as base64 content.
INPUTS: fileName / fileContent / userPassword / adminPassword / pdfPrivileges
unlock_pdf_documentREVIEWRemove password protection from one PDF document and return the unlocked PDF as base64 content.
INPUTS: fileName / fileContent / password
INPUT CONTRACTS
Know what the action needs before it runs.
get_pdf_text_layer
fileNameREQUIRED- The source PDF file name, including the .pdf extension required by Encodian.
fileContentREQUIRED- The base64-encoded PDF document content to process.
startPageOPTIONAL- The first one-based page number to include when extracting the text layer.
endPageOPTIONAL- The last one-based page number to include when extracting the text layer.
textEncodingTypeOPTIONAL- The text encoding Encodian should use for the extracted PDF text layer.
compress_pdf
fileContentREQUIRED- The base64-encoded PDF document content to process.
compressImagesOPTIONAL- Whether Encodian should compress images embedded in the PDF document.
imageQualityOPTIONAL- The image quality percentage used when image compression is enabled.
maxResolutionOPTIONAL- The maximum image resolution in DPI before Encodian scales oversized images down.
resizeImagesOPTIONAL- Whether Encodian should resize images larger than the maximum resolution.
extract_pdf_pages
fileContentREQUIRED- The base64-encoded PDF document content to process.
startPageOPTIONAL- The first one-based page number to extract.
endPageOPTIONAL- The last one-based page number to extract. Leave empty to continue to the final page.
pageNumbersOPTIONAL- A comma-separated list of one-based page numbers to extract, such as '1,3,4'.
secure_pdf_document
fileNameREQUIRED- The source PDF file name, including the .pdf extension required by Encodian.
fileContentREQUIRED- The base64-encoded PDF document content to process.
userPasswordOPTIONAL- Optional password required to open the protected PDF document.
adminPasswordOPTIONAL- Optional password required to edit the protected PDF document.
pdfPrivilegesOPTIONAL- The Encodian privilege mode applied to the protected PDF document.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Pdf Text Layer
Extract the text layer from one PDF document with optional page-range and encoding controls. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_pdf_text_layerVerify with Compress Pdf
Compress one PDF document with Encodian and return the optimized PDF file as base64 content. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
compress_pdfSAFETY BOUNDARY
Operate Encodian with explicit limits
- Authorize Encodian with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Encodian data may still be sensitive and should be minimized before it enters model context.
- 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 Encodian rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Encodian task completed successfully.
CONNECTION MODEL
API key
Encodian API key sent with the X-ApiKey header. Generate or manage keys from the Encodian API key portal: https://www.encodian.com/apikey/.
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
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
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 Encodian.