Claude PDF.net connectorWhat Claude can do in your PDF.net account.
The Claude PDF.net connector exposes 20 tools. 4 read your library, 12 change it, 4 are undocumented. Below: what Claude can produce and rearrange in your PDFs, what still needs the web editor, and where the official texts disagree.
Verified Trustpilot reviews · AI, automation & growth agency
PDF chores, done from the conversation
Fixing a date in a contract, stitching three files into one, shrinking a report for email: each PDF task usually means another app or a detour through Word. With the connector, you tell Claude what you want, it works on the files in your PDF.net library and hands you back a download link.
Prepare a deal package. merge_pdf_documents combines the contract, its annex and the invoice in the order you give, then compress_pdf_document shrinks the result before download_pdf_document returns the link.
Correct a contract without Word. describe_editor_pages reads the page structure, then apply_editor_command replaces an old company name everywhere and updates the effective date, directly inside the PDF.
Start from nothing. Describe an invoice or a proposal and generate_pdf_document builds a formatted PDF, saves it to your library and gives you the link.
Now the part the directory sheet leaves out. E-signing, annotations, form filling and password protection are not available through the connector yet: Claude sends you to the PDF.net web editor instead. Four listed tools have no description anywhere. And nothing runs on its own when a file lands in a folder. For that kind of background job, an automation tool fits, which is a different trade; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you'll meet while plugging PDF.net in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as PDF.net.
Plug PDF.net into Claude in three steps
- 01
Find PDF.net in Claude
In Claude's settings, open Customize, then Connectors, and look for PDF.net in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first, then each member signs in.
- 02
Start the connection
Click Connect on the PDF.net row, then sign in to PDF.net in the window PDF.net opens itself. If that link ever breaks later on, use Disconnect and plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to PDF.net, not to Claude, so PDF.net decides what the access covers. You can withdraw that access later from the PDF.net side too.
The 20 tools, sorted by what they do
PDF.net gives Claude 20 tools: 4 that read your account, 12 that change something in it, and 4 no official source describes.
Three groups: what Claude reads, what it changes in your library, and what no official source describes. The names stay exactly as Claude shows them.
- 4 read
- 12 write
- 4 not documented
What Claude reads (4)
4 toolsFour tools that look into your documents without changing them.
describe_editor_pages
Reads the layout of a document: its pages, its paragraphs and where each sits. Claude needs this map before it can touch a precise passage.
download_pdf_document
Hands you a direct download link for any document in your PDF.net library. Most requests end right here, once the work on the file is saved and you simply want it on your own computer or phone.
list_document_tree
Lists what sits in your library, documents and folders. PDF.net recommends it when Claude can't find a file: listing refreshes the IDs Claude works with.
open_in_web_editor
Returns a direct link that opens a document in the PDF.net web editor. Claude falls back on it for features the connector can't handle yet.
What Claude changes (12)
12 toolsTwelve tools that create, modify or remove files and folders. No source gives them their own confirmation rule: the general rule below applies.
apply_editor_command
Approval: see the ruleApplies targeted changes inside a PDF, paragraph by paragraph: replacing text, alignment, line spacing, indentation, adding or removing pages and text blocks, bold or italic styling.
compress_pdf_document
Approval: see the ruleReduces the size of a PDF, with three levels to choose from: low, medium or high compression.
convert_pdf_document
Approval: see the ruleExports a document to another format: DOCX, XLSX, PPTX, TXT, HTML, PNG, JPG and more.
copy_pdf_document
Approval: see the ruleDuplicates a document in your library, so a second version can change while the first one stays as it was.
create_folder
Approval: see the ruleCreates a folder in your PDF.net library, so documents can be sorted by type, client or project.
delete_resource
Approval: see the ruleRemoves a document or a folder from your library. It is the only listed tool whose whole purpose is deletion.
generate_pdf_document
Approval: see the ruleBuilds a complete, formatted PDF from a plain-language description: or a template filled in with details such as a client name, an amount or a date. The result is saved to your library automatically.
import_file_from_url
Approval: see the ruleBrings a file into your PDF.net library from a web address. PDF, DOCX, XLSX, PPTX, PNG, JPG and other formats are accepted; non-PDF files get converted automatically.
merge_pdf_documents
Approval: see the ruleCombines several documents into one PDF, in the order you choose, up to 20 files at once.
move_resource
Approval: see the ruleMoves a document or a folder to another place in your library. Combined with the listing, it lets Claude tidy a whole library in one request.
rename_resource
Approval: see the ruleGives a document or a folder a new name. Useful when a batch of generated files should carry the client's name.
split_pdf_document
Approval: see the ruleExtracts specific pages or page ranges as separate documents. You say which pages go where, and each part becomes its own file.
Undocumented (4)
4 toolsThe directory publishes these four names and nothing else. No official text says what they do, and a name is not enough to guess.
find_in_documents
This name is in the directory's tool list, and that is all anyone publishes about it. PDF.net's help article doesn't mention it and no Claude page does either, so this page goes no further.
get_profile
Shown by name on the directory sheet, with no official sentence explaining it, from PDF.net or from Anthropic. Nothing more can be said without guessing, and this page won't guess.
open_pdf_document_editor
Another listed name without a description of its own. PDF.net's article talks about editing in general terms, but never names this tool, so no source says what it does.
open_pdf_document_manager
The fourth name the directory lists without explanation. No help page, from either side, explains its role in your library, what it returns, or when Claude would call it.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the chat, at the moment it matters.
That matters here: twelve tools change your library, deletion included. On a Team or Enterprise workspace, owners decide whether a member can let some actions through without being asked every time. They can also restrict what a connector may do for the whole organization, for example keep reading open and close every write, and nobody overrides that from their own account. PDF.net adds that every tool is scoped to your own authenticated account.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. The connector-by-connector answer is published nowhere: it is a real gap in the catalogue, not a miss in our research.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. For the current state of this one, check the PDF.net sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a file is uploaded, a contract is signed or a folder fills up.
Only PDF.net documents this connector; no Claude help page covers it. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. PDF.net also advertises full document translation that keeps the layout, without tying it to any listed tool. For comparison with another connector, see the Claude asana connector.
Can Claude fill in a PDF form through the PDF.net connector?
- Claude directory sheet ↗September 2026Edit PDFs in place, including fixing dates and filling forms.
- PDF.net help center ↗September 2026Form filling is among the features not available through the connector yet; the assistant links to the web editor instead.
What this page followsThe two texts disagree and the directory sheet carries no date of its own. PDF.net's help article is the more detailed on this point, so this page follows it: expect form filling to happen in the web editor, not in the conversation, until PDF.net says otherwise.
Need help connecting PDF.net to Claude?
A person reads every message.
