Claude Docfarm connectorWhat Claude can do in your Docfarm account.
The Claude Docfarm connector exposes 22 tools. 9 read your docs and their stats, 12 write, and 1 is undocumented. Below: how Claude publishes a page behind a share link, edits it in place, tracks who viewed it, and which tools can overwrite or delete for good.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can publish to Docfarm
Claude writes a proposal, a one-pager or a report; Docfarm turns it into a live page with a share link. Ask for a change later and Claude patches that page in place, so the link you already sent shows the latest version. Docfarm also records who opened each doc and what they read, which Claude can use to prepare your follow-up.
From chat to a link. host_html_content puts an HTML doc on Docfarm and hands back its share link. Reusing the same name updates that doc and keeps its link, password and view stats.
Small fixes, small edits. get_doc_html reads the current page, then patch_doc swaps one snippet, or patch_doc_batch applies several at once, all or nothing.
Know who read it. get_doc_status shows viewing stats, and draft_followup pulls that viewing data so Claude can prepare a follow-up email for you to send.
Now the part to watch. Twelve tools change something, and some are final: delete_doc removes a doc with its links, analytics, comments and stored file, with no way back. Inviting a collaborator reaches a real person, by email if they are not on Docfarm yet. Claude also acts only while it answers you: nothing is republished or chased up on its own. A scheduled reminder after a prospect opens a proposal belongs to an automation tool, a different job; the Integrations hub covers that side. For a connector that manages web content on a CMS instead, see the Claude agility-cms connector.
Five words before you connect
The Claude terms used around this connector, explained once.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector gives Claude, such as hosting or patching a doc. Claude picks the tools itself; the directory lists all 22.
- Authorization
- Docfarm's own sign-in screen, where you grant the access Claude will use. Given once per person, and it can be withdrawn later.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes your account, shown right in the conversation.
- MCP
- The common standard connectors are built on, the piece that lets an assistant like Claude talk to an outside service such as Docfarm.
Connect Docfarm to Claude in three steps
- 01
Find Docfarm in Claude
Open Claude's settings, go to Customize, then Connectors, and look up Docfarm. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before members can each sign in.
- 02
Sign in to Docfarm
Click Connect on its row and log in in the window Docfarm opens. That window belongs to Docfarm, not Claude. If the link breaks later, use Disconnect and connect again.
- 03
Review the access
Read Docfarm's authorization screen before accepting it. It is the service that sets what the access covers. You can also withdraw that access later from the Docfarm side.
The 22 tools: what Claude reads, writes, and what is unknown
Docfarm gives Claude 22 tools: 9 that read your account, 12 that change something in it, and 1 no official source describes.
Three groups: what Claude looks at, what it changes, and the one tool no source describes. Names stay exactly as Claude shows them.
- 9 read
- 12 write
- 1 not documented
What Claude reads (9)
9 toolsNine tools that look at your docs, links and viewing stats, and leave them as they are.
draft_followup
Gathers the viewing data of one doc so Claude can prepare a follow-up email based on what the reader actually opened.
get_doc_html
Returns the current HTML of any doc you can access, yours or shared with you, with its title, share link and your role on it.
get_doc_status
Pulls the viewing statistics of a doc, the figures Docfarm keeps on who opened it and how they read it.
get_doc_url
Produces a time-limited link to the raw file of any doc you can access, whether HTML, PDF, Markdown or something else stored on Docfarm.
get_share_link
Retrieves the share URL of an existing doc, the address your readers open in their browser.
get_tracking_snippet
Returns the tracking snippet attached to an HTML doc, the piece of code that lets Docfarm count views.
list_docs
Lists the docs you own in your Docfarm space; those other people opened to you sit in a separate list.
list_shared_with_me
Shows the HTML docs other Docfarm users added you to as a collaborator, and for each one how your future contributions would be handled: on the original or in a copy of your own.
whats_possible
Gives a grouped overview of the capabilities Docfarm offers inside Claude, from reading and tracking to collaboration and follow-ups.
What Claude changes (12)
12 toolsTwelve tools that publish, edit, share, rename or delete. No source spells out a Claude prompt for them, so the general rule below applies.
delete_doc
Approval: see the rulePermanently removes a doc you own along with its share links, view data, chat, comments, suggestions, collaborators and stored file. There is no undo.
duplicate_doc
Approval: see the ruleCopies a doc you can read, yours or shared, into your own space under a new name, server-side, so the content does not pass through the conversation.
finalize_upload
Approval: see the ruleSecond step of a large upload: publishes the file sent to the signed address, and a new name gives a new doc with its own share link.
get_upload_url
Approval: see the ruleFirst step for publishing a large HTML file from disk: returns a short-lived signed address to send it to, before the finishing step.
host_html_content
Approval: see the rulePublishes an HTML doc on Docfarm and returns its share link. A new name makes a new doc; an existing name overwrites that doc, keeping its link, password and stats.
invite_collaborator
Approval: see the ruleInvites someone by email to work on a doc you own, either editing the original or forking their own copy. A non-user gets an invite email with a sign-up link.
patch_doc
Approval: see the ruleEdits a hosted doc by replacing one snippet of its HTML, from a typo to a new section, without republishing the whole page.
patch_doc_batch
Approval: see the ruleApplies several snippet edits to one doc atomically, so either every change lands or none does.
propose_edit
Approval: see the ruleSends the owner of a doc you collaborate on a suggestion instead of changing it: either a comment, or a copy carrying your edit.
rename_doc
Approval: see the ruleChanges the display title of a doc you own and deliberately keeps its share link, so links already sent keep working.
track_html_page
Approval: see the ruleRegisters a page you already host elsewhere, such as your site, for visitor tracking, and returns a script tag to paste into that page.
update_doc_settings
Approval: see the ruleChanges the sharing settings of a doc you own: password, asking viewers for their name, file downloads and view notifications. Only the fields passed are touched.
Undocumented (1)
1 toolThis name is on the directory sheet and nowhere else we could read. No official text says what it does, and we will not guess from the name.
read_shared_doc
This name appears in the directory's tool list, but the list Docfarm's server publishes does not include it, and no other official text describes it. This page therefore says nothing about what it does. No source says whether it reads or changes anything in your account.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account on someone's behalf. That default matters here, with twelve tools that change your docs.
Only one tool carries an instruction of its own: Docfarm's server tells Claude to confirm with you before deleting when the request is ambiguous. On Team and Enterprise, owners decide whether members may let some actions through without a prompt, and they can restrict a connector for the whole organization, reading on and writing off for example. Claude works with your own Docfarm access and nothing beyond it.
Which plans can use it
None of the 819 sheets in the official directory shows plan availability. For Docfarm, as for every connector, that answer is published nowhere.
The documented rule is a general one: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. The live state of this one sits on its sheet in the official directory, the only place kept current.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing is republished or followed up when a reader opens a doc.
The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees how they behave. Everything on this page comes from the directory sheet and from the tool list Docfarm's server publishes; no Claude help article covers this connector. That server list also holds tools the directory does not show, which this page deliberately leaves aside.
Need help connecting Docfarm to Claude?
A person reads every message.