Resources · Claude connector

Claude PDF Tools connectorWhat Claude does with your PDFs, right on your own computer.

The Claude PDF Tools connector exposes 43 tools. 16 read your PDFs, 13 can change them or produce files, 14 have no established direction. Below: what Claude does with your documents locally, what it can rewrite, and which folders to open to it first.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes if you handle PDFs all day

PDF Tools turns Claude Desktop into a PDF workshop that runs on your own machine, without shipping files off to an online PDF service. Claude reads, searches, fills in, signs, merges or splits your documents while it answers you. One limit to know upfront: there's no text recognition on scanned pages.

Fill in forms in bulk. When the same details keep coming back, save_profile stores them as a profile, fill_with_profile applies them, and bulk_fill_from_csv fills several PDFs from a spreadsheet export.

Get a document ready to sign. detect_signature_zones finds where to sign, initial or date, then apply_signature and apply_text place a signature, date or text on those spots, locally.

Reorganize a file. merge_pdfs combines several PDFs into one, split_pdf breaks a report up by page range, and apply_page_plan reorders, rotates and deletes pages in one pass while keeping the original.

What Claude doesn't do here: no remote version for Cowork or Claude on the web, since it targets Claude Desktop and other local hosts; no optical recognition of scans; and fourteen tools that no source pins down as read or write. Nothing runs in the background either. To process PDFs as they arrive you need an automation tool, a different job; the Integrations hub covers that side.

Vocabulary

The vocabulary in one minute

Five words that come up below.

Connector
What you install once to open a tool or service to Claude; here, an extension that works on your own disk.
Tool
A named action the connector makes possible. Claude picks which ones to call by itself, and the directory sheet lists them.
Desktop extension
A connector installed in the Claude Desktop app, acting on the machine's own files rather than online.
Approval
The confirmation Claude asks for before an action that changes something, shown in the chat at the right time.
MCP
The open standard that links connectors to Claude; it's how the assistant drives PDF Tools.
Connect

Install PDF Tools in Claude in three steps

  1. 01

    Open Claude Desktop

    PDF Tools targets Claude Desktop and doesn't offer a remote connector yet. Open the settings, then Customize and Connectors, and find PDF Tools. On Team or Enterprise, an Owner or Primary Owner has to enable it first.

  2. 02

    Add it

    Click Connect on its row. No account is involved: the extension works on your local files. If the install goes sideways, use Disconnect and start over.

  3. 03

    Pick the folders it can reach

    The extension's settings include an allowed directories field. If a service ever shows you an authorization screen, read it before accepting: that screen, not Claude, sets how far access goes.

Tools

The 43 tools, grouped by what they do

PDF Tools gives Claude 43 tools: 16 that read your account, 13 that change something in it, and 14 no official source describes.

Three groups: what Claude reads, what can change a file, and what no source sorts clearly. Names stay in English.

  • 16 read
  • 13 write
  • 14 not documented

What Claude reads (16)

16 tools

Sixteen tools that display, read, search or analyze your PDFs without changing them.

display_pdf

Opens a PDF in the interactive viewer: page navigation, zoom, search, fullscreen, text selection and a sidebar showing form fields with their fill status.

When it helps
a PDF on your computer needs to be read page by page, with its form fields in view.

Sourcegithub.com · October 1, 2026 ↗

load_profile

Opens a stored profile, one of those reusable sets of personal or business details, so Claude knows what's in it before filling anything.

When it helps
a saved profile is about to fill a form and you want to see its contents first.

Sourcegithub.com · October 1, 2026 ↗

list_profiles

Shows the profiles already saved, those sets of personal or business details kept for reuse. The publisher pitches listing, loading and applying them as the way to get repeated forms done in seconds rather than minutes.

When it helps
you need to know which saved profiles exist before picking one.

Sourcegithub.com · October 1, 2026 ↗

validate_pdf

Checks that a form has every required field filled in before it goes out the door. The publisher pairs it with bulk filling from a spreadsheet.

When it helps
a batch of forms has been filled and the required fields must be checked before submission.

Sourcegithub.com · October 1, 2026 ↗

read_pdf_content

Reads a PDF's existing text layer for a summary, a specific question or research. If the result has no text, the tool can return an image of page 1 instead.

When it helps
a document with a text layer needs a summary or an answer to a precise question.
Watch out
with no recognition engine, a scanned page after page 1 can stay unreadable.

Sourcegithub.com · October 1, 2026 ↗

read_pdf_pages

Reads a bounded set of pages instead of the whole document. Handy for keeping the answer focused on a long file without flooding the chat.

When it helps
only a page range of a long document matters to the question.

Sourcegithub.com · October 1, 2026 ↗

convert_pdf_to_markdown

Turns pages into Markdown text, rebuilding tables backed by the document and checked web links. Doubtful links stay as plain text and get flagged as typed gaps.

When it helps
a born-digital document has to be reused as Markdown text, tables included.

Sourcegithub.com · October 1, 2026 ↗

verify_table_proposal

Holds a proposed table up against the original PDF and only returns it if text and layout match. An unclear table stays unconverted for a human to look at.

When it helps
a table has been rebuilt from a PDF and has to be checked against the original before use.

Sourcegithub.com · October 1, 2026 ↗

render_pdf_page

Turns a whole page into a PNG image so the model can look at it, which is what scanned or image-heavy documents call for. The publisher insists the result is a raster picture, not recognized text.

When it helps
a scanned page has no text layer and has to be inspected visually.

Sourcegithub.com · October 1, 2026 ↗

render_pdf_region

Captures one bounded region of a page as a PNG image, a signature block for instance, rather than the whole page. As with full-page renders, the publisher stresses that what comes back is a picture, not recognized text.

When it helps
only one part of a page matters, such as a signature block.

Sourcegithub.com · October 1, 2026 ↗

search_pdf_text

Looks for a term in the PDF's text and finds every occurrence. Useful for checking a clause across a whole document without reading all of it.

When it helps
a term has to be found everywhere it appears in a long document.

Sourcegithub.com · October 1, 2026 ↗

inspect_pdf_accessibility

Runs a bounded structural check on an unencrypted local PDF, flagging missing or unavailable signals. The publisher warns it reaches no compliance conclusion.

When it helps
a document's structure needs a first screen before a full accessibility review.
Watch out
it doesn't replace a PDF/UA audit or a WCAG review, and human review is still required.

Sourcegithub.com · October 1, 2026 ↗

compare_pdfs

Compares documents with each other: the directory sheet lists comparison among what the connector does with a PDF already on your computer, next to merging and splitting. No source details how the differences are reported.

When it helps
two versions of a document have to be set against each other.

Sourceclaude.com · October 1, 2026 ↗

get_pdf_info

Gathers observations about a file tied to its SHA-256 fingerprint, keeps form annotations apart from ordinary ones and returns links as inert values.

When it helps
you need a file's observations tied to its exact SHA-256, with links kept inert.

Sourcegithub.com · October 1, 2026 ↗

get_page_analysis

Inspects each page for orientation, whether there's text, images and likely blank pages. The publisher files it with its extraction and analysis tools, and it shows quickly which pages need a closer look.

When it helps
a long scan may contain blank or misoriented pages that need spotting.

Sourcegithub.com · October 1, 2026 ↗

detect_signature_zones

Detects likely signature, initials, printed-name and date zones, with coordinates Claude can reason from in a next step, such as placing a signature. The publisher presents it as part of its Sign mode.

When it helps
you need to know where a document expects signatures, initials, names and dates.

Sourcegithub.com · October 1, 2026 ↗

What can change a file (13)

13 tools

Thirteen tools that fill in, sign, reorganize or download PDFs. No source describes their confirmation, so the general rule applies.

fill_pdf

Approval: see the rule

Fills in a PDF form with fields: W-9s, tax forms, rental applications, waivers, any fillable PDF.

What Claude asks for
no source describes a confirmation specific to this tool, so the general rule applies.
When it helps
a fillable form such as a W-9 or a rental application has to be completed from details you give Claude.

Sourcegithub.com · October 1, 2026 ↗

bulk_fill_from_csv

Approval: see the rule

Fills in many PDFs from the rows of a CSV file, the kind of table you export from a spreadsheet.

What Claude asks for
no confirmation rule is documented for bulk filling; Claude's own takes over.
When it helps
the same form has to be produced once per row of a table.

Sourcegithub.com · October 1, 2026 ↗

save_profile

Approval: see the rule

Stores personal or business details as a reusable profile.

What Claude asks for
the docs don't provide for a dedicated confirmation; Claude applies its default setting.
When it helps
the same personal or business details keep coming back from one form to the next.

Sourcegithub.com · October 1, 2026 ↗

fill_with_profile

Approval: see the rule

Applies a stored profile to a form so the same details land in the right fields without retyping.

What Claude asks for
the sources say nothing about a specific approval; the general rule applies.
When it helps
a new form asks for details already stored in a profile.

Sourcegithub.com · October 1, 2026 ↗

merge_pdfs

Approval: see the rule

Combines several PDFs into a single document. The result is a new file.

What Claude asks for
no page documents a go-ahead specific to merging; Claude's shared rule is what applies.
When it helps
several PDFs have to travel as a single document.

Sourcegithub.com · October 1, 2026 ↗

split_pdf

Approval: see the rule

Splits a PDF by exact page ranges or at regular intervals.

What Claude asks for
no source mentions a confirmation for splitting; Claude's approval setting decides.
When it helps
parts of one PDF have to be handled as separate files.

Sourcegithub.com · October 1, 2026 ↗

rotate_pdf_pages

Approval: see the rule

Rotates pages in a PDF, by a quarter turn for instance, to straighten a crooked scan.

What Claude asks for
no dedicated sign-off rule is described; the general approvals rule covers it.
When it helps
some pages of a scan come out in the wrong orientation.

Sourcegithub.com · October 1, 2026 ↗

reorder_pdf_pages

Approval: see the rule

Changes the order of a PDF's pages without adding or removing any.

What Claude asks for
no dedicated confirmation shows up in the sources; Claude follows its default.
When it helps
the pages are all there but not in the right order.

Sourcegithub.com · October 1, 2026 ↗

apply_page_plan

Approval: see the rule

Applies a full page plan in one pass: reorder, rotate and delete, while keeping the original, per the publisher.

What Claude asks for
the sources describe no request for consent on this plan; Claude's rule applies.
When it helps
several page changes, reordering, rotating and deleting, have to happen in one pass.

Sourcegithub.com · October 1, 2026 ↗

fetch_pdf_from_url

Approval: see the rule

Downloads a PDF from a web address to your machine, into a folder you've allowed, so it can be opened in the viewer next.

What Claude asks for
no source talks about a confirmation before this download; the general rule holds.
When it helps
you have a PDF's direct link, including when Claude's web fetch is blocked.

Sourcegithub.com · October 1, 2026 ↗

add_signature_field

Approval: see the rule

Adds signature and date boxes to a PDF where the document didn't have any.

What Claude asks for
the docs specify no sign-off specific to this addition; Claude's setting decides.
When it helps
a document needs signature or date zones placed on it.

Sourceclaude.com · October 1, 2026 ↗

apply_signature

Approval: see the rule

Places a signature on a detected or custom zone, using local signatures. The publisher describes edits that stay on your machine.

What Claude asks for
no specific confirmation rule is published for signing; Claude's general rule covers the tool.
When it helps
a saved local signature has to go on a detected or custom zone.

Sourceclaude.com · October 1, 2026 ↗

apply_text

Approval: see the rule

Places a date or other text on a detected or custom zone of the PDF.

What Claude asks for
the sources stay silent on a dedicated confirmation; Claude applies its common rule.
When it helps
a date or other text is missing from a zone of the document.

Sourceclaude.com · October 1, 2026 ↗

Direction unclear (14)

14 tools

The sheet lists these names; some get a mention from the publisher, others none at all. No source says whether they read or write, and we won't guess.

list_pdfs

This name shows up on the sheet and in the publisher's list without a line of explanation. No official source describes it, so this page assigns it no role.

Watch out
whatever it does, the general approvals rule covers it.

read_pdf_fields

The publisher names it among its form tools, next to filling and profiles, without saying exactly what it does. No source establishes whether it reads or changes anything.

Watch out
lacking detail, rely on Claude's default rule rather than an assumption.

extract_to_csv

Per the publisher, it handles extracting structured data to a CSV file. No source says whether it writes that file to your disk or just returns its contents.

Watch out
until that's documented, the general approvals rule is what applies.

read_pdf_layout

The sheet publishes this name and nothing else. Neither the publisher's guide nor Anthropic offers any description of it, and we won't interpret it from the name alone.

Watch out
it stays under Claude's general rule, like the rest of the list.

get_pdf_resource_uri

No published documentation describes this tool. All we know is that the publisher files it under its viewer and reading tools, with no further detail.

Watch out
don't count on any specific behavior; only the general approvals rule is certain.

get_pdf_identity

The publisher lists this name without describing it anywhere, and Anthropic has nothing on it either. It is one of eight tools on the sheet with no descriptive sentence at all. No source says what it returns or whether it changes anything.

Watch out
Claude's default rule is what applies to it.

create_signature

The publisher talks about drawing or reusing saved local signatures, one sentence that covers three tools without telling them apart. No source says whether this one creates, reads or changes anything.

Watch out
the general approvals rule is the only certainty about it.

get_allowed_directories

Filed by the publisher under its active-document helpers, this name has no descriptive sentence anywhere, from the publisher or from Anthropic. This page therefore assigns it no function.

Watch out
like the others, it falls under the general approvals rule.

list_signatures

The second tool covered by that same sentence about saved signatures. Nothing in the sources sets it apart from the other two, or says whether it only reads.

Watch out
don't infer its effect from its name; the general rule applies.

load_signature

The third name tied to that same mention of reusable signatures, with no description of its own. No source establishes its direction, read or write, and this page doesn't fill that gap.

Watch out
only Claude's default rule covers it with certainty.

get_active_document

Active-document tracking during signing appears in the publisher's text, but this particular tool goes undescribed. No source says what it returns or how it acts on your files.

Watch out
it stays under the general approvals rule, for lack of anything better.

set_active_document

Same situation as its neighbor: the idea of an active document appears in the publisher's text, but no source documents this tool, and its direction is still unknown today.

Watch out
don't expect any particular behavior; Claude's common rule applies.

prepare_signing_packet

The publisher describes preparing a provider-neutral handoff receipt bound to the exact local input and output, zones, roles and page geometry, without contacting a signing provider. No source says whether it writes that receipt to a file.

Watch out
whether it reads or writes isn't established; the general rule covers it.

reveal_in_finder

The last name in the publisher's list of helpers, with not a single sentence to explain it. No source describes it, and this page sticks to flagging that silence.

Watch out
like every undocumented tool, it falls under the general approvals rule.
Approvals

What Claude asks before acting

By default, Claude stops and asks for your go-ahead before every action it takes for you on an account or service. The request shows up in the chat, at the moment it matters.

No source describes a confirmation specific to the thirteen tools that change a file, or to the fourteen with no established direction. The publisher does describe file-side safeguards: by default the extension reaches only Documents, Downloads and Desktop plus the folders you add, and it keeps a backup when signing changes the same file. On Team and Enterprise, Owners decide whether a member may let some actions through without a fresh prompt, and can restrict the connector for the whole organization.

Plans

Which plans it's available on

None of the 819 sheets in the official directory shows plan availability. Per connector, that information isn't published anywhere.

The general rule is published: desktop extensions install in Claude Desktop, and remote connectors are open on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables them for the organization before members use them. The current state shows on the PDF Tools sheet in the official directory.

Limits

Where this connector stops

A connector isn't an automation. Claude calls these tools while it answers you, so no PDF fills itself in while you're away.

The tool list is an observed floor, not a ceiling: an admin can open actions that appear on no public sheet. This connector is documented by its publisher alone, whose guide also lists e-signing tools missing from the sheet; the rest of the family sits on the Claude connectors hub. Anthropic says on every sheet that it doesn't vouch for how the exposed tools behave, so add only publishers you trust.

Need help

Need help connecting PDF Tools to Claude?

A person reads every message.

FAQ

FAQ about the Claude PDF Tools connector

01What can Claude do with the PDF Tools connector?
Claude can work on your PDFs locally in Claude Desktop: display, read and search them, convert them to Markdown, analyze them page by page, fill in forms one at a time or in bulk, place signatures and dates, and merge, split, rotate and reorder pages. Sixteen tools read, thirteen can change or produce files, and fourteen have no direction established by a source. It all happens on your machine rather than in an online PDF service.
02Can Claude change or overwrite my PDFs?
Yes, thirteen tools can change a file: filling in, signing, placing text, merging, splitting, rotating, reordering, applying a page plan or downloading a PDF from the web. The publisher says the page plan keeps the original and that a backup accompanies signing edits on the same file. For the other tools, no source details what happens to the original,, and the publisher adds that page reorganization saves its output as a new file.
03Does Claude ask before filling in or signing a PDF?
By default, Claude asks for confirmation before every action it takes on your behalf. No source describes a rule specific to PDF Tools, so that default is what applies, signing included. On Team and Enterprise, Owners decide whether members can let some actions through without a prompt, and they can restrict the connector for the whole organization, with no way around it from a personal account. Signing gets no special treatment in the sources.
04Which plans is the PDF Tools connector available on?
No official source publishes plan availability for this connector, and no directory sheet shows it. Anthropic's general rule: desktop extensions install in Claude Desktop, remote connectors are open on Claude, Cowork, Claude Desktop and mobile, and on Team or Enterprise an Owner enables them first. PDF Tools is a desktop extension, tied to the installed app. The directory sheet, opened from your own account, is still the only current view of where things stand.
05Does Claude see every file on my computer?
No. By default, PDF Tools only reaches Documents, Downloads and Desktop, and any other folder has to be added to the allowed directories field in its settings. The publisher says it reads, renders, edits and saves files on your machine rather than uploading them to a separate PDF service, though what it returns to Claude falls under your model provider's data terms. On top of that, a Team or Enterprise Owner can restrict the connector for the whole organization, whatever folders each machine opens.
06Why can't Claude read my scanned PDF?
Because PDF Tools ships no optical character recognition engine. Reading relies on the PDF's text layer; if it's empty, the reading tool can return an image of page 1 for a visual check. Other scanned pages may therefore slip through. You can ask Claude to render a page or region as an image so it can look at it, knowing the publisher lists local recognition as a planned improvement rather than a shipped one.
07Claude or an automation tool for my PDFs?
They do different jobs. Claude with PDF Tools fits when you're working a file right now: filling in a form while you talk, checking a clause, prepping a contract for signature. An automation tool fits when PDFs have to be handled without you, as they arrive or on a schedule. None of the connector's tools starts on its own, so automatically filling in every form that lands in your inbox belongs with the second kind of tool.