ChatPDF MCP integration for AI agents.
Connect AI agents to ChatPDF through 3 structured actions, including add source url, delete sources, and chat. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 3
- 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 ChatPDF integration exposes
The ChatPDF Agent App exposes 3 provider-backed actions for ai and productivity work. Its current contract lets an authorized agent import a publicly reachable pdf url into chatpdf and return its source id, delete one or more imported pdf sources from chatpdf, and ask chatpdf one or more stateless questions about an imported pdf source. 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 ChatPDF account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ChatPDF capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_source_urlWRITEImport a publicly reachable PDF URL into ChatPDF and return its source ID.
INPUTS: url
delete_sourcesHIGH IMPACTDelete one or more imported PDF sources from ChatPDF.
INPUTS: sources
chatREVIEWAsk ChatPDF one or more stateless questions about an imported PDF source.
INPUTS: sourceId / messages / referenceSources
INPUT CONTRACTS
Know what the action needs before it runs.
add_source_url
urlREQUIRED- The publicly reachable URL of the PDF to import.
delete_sources
sourcesREQUIRED- The source IDs to delete.
chat
sourceIdREQUIRED- The ChatPDF source ID for the imported PDF.
messagesREQUIRED- The stateless conversation sent to ChatPDF.
referenceSourcesOPTIONAL- Whether ChatPDF should include inline page citations and reference metadata.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add Source Url
Import a publicly reachable PDF URL into ChatPDF and return its source ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_source_urlControl Add Source Url
Import a publicly reachable PDF URL into ChatPDF and return its source ID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_source_urlVerify with Delete Sources
Delete one or more imported PDF sources from ChatPDF. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
delete_sourcesSAFETY BOUNDARY
Operate ChatPDF with explicit limits
- Authorize ChatPDF with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_sources` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ChatPDF rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ChatPDF task completed successfully.
CONNECTION MODEL
API key
ChatPDF API key sent in the x-api-key header. View your key in the ChatPDF backend API documentation after signing in: https://www.chatpdf.com/docs/api/backend.
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
- 0
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
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 ChatPDF.