# Docfarm — AI Connector Docfarm publishes 22 MCP tools to Claude. Marketplace availability, tool surface, verification tier, and what Node8 measured against the live endpoint. Source: https://node8.ai/ai-connectors/productivity/docfarm/ --- [AI Connectors](https://node8.ai/ai-connectors/) · [Productivity](https://node8.ai/ai-connectors/productivity/) # Docfarm Host, share and patch AI-generated documents with view tracking Listed in Claude · 22 published tools · Community-listed [Claude connector docs](https://doc.farm/library) [doc.farm](https://doc.farm/) Overview ## What Docfarm does Docfarm publishes what a model produces to a hosted page with a stable share link, then edits that page in place, so a link already sent to someone keeps showing current content. It records who opened a document, how far into it they got and how long they spent, and can draft a follow-up from that data. Documents can be password protected, renamed without changing the slug, duplicated, or opened to collaborators, who may propose an edit instead of applying one. Pages hosted elsewhere can be registered for the same tracking with a script tag. A Docfarm account is required, and the connector carries community tier. ### Who it is for Consultants and salespeople who send documents and want to know whether they were read. ### Tool surface The endpoint returned twenty-one tools against a claimed twenty-two, and the naming is unusually explicit about ownership: list\_docs versus list\_shared\_with\_me, patch\_doc versus propose\_edit, plus a get\_upload\_url and finalize\_upload pair that keeps large files out of the model's context entirely. Availability ## Where Docfarm is listed Docfarm is listed in the Claude connectors directory only. Docfarm has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them. The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one. Claude listing ## In the Claude connectors directory Docfarm publishes 22 tools to Claude, deeper than 72.2% of the 1,253 Claude-listed connectors. The median Claude-listed connector filed under Productivity publishes 12, so this one runs 10 tools above its bucket's median and ranks 133rd of 462 by tool count. It falls in the 21-50 tools band, which holds 20% of the Claude directory. ### Measured against the live endpoint A direct call to the endpoint returned 21 tools, 1 fewer than the 22 the listing publishes. Probed 2026-08-07. #### Tools the server actually returns - `whats_possible` - `list_docs` - `get_share_link` - `get_doc_status` - `track_html_page` - `get_tracking_snippet` - `update_doc_settings` - `rename_doc` - `delete_doc` - `invite_collaborator` - `draft_followup` - `host_html_content` - `duplicate_doc` - `get_upload_url` - `finalize_upload` - `get_doc_html` - `get_doc_url` - `patch_doc` - `patch_doc_batch` - `list_shared_with_me` - `propose_edit` Docfarm publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally. Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there. Publisher Docfarm Verification Community-listed (61.5% of the Claude directory) Filed under Productivity Endpoint `https://mcp.doc.farm/` Documentation [Publisher setup docs](https://doc.farm/library) Published tools 22 · 21-50 tools band Depth rank in Productivity 133 of 462 Snapshot August 2026 Docfarm is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality. In the publisher's words ## How Docfarm describes it > Docfarm turns anything Claude makes into a living, trackable document. Ask for a share link and Claude publishes the page to your farm in seconds; ask for a change and it patches the live doc in place (token friendly) — the link you already sent always shows the latest version. See who viewed each doc, which pages they read, and for how long. Duplicate and remix existing docs, protect them with passwords, invite collaborators, and draft follow-ups based on real engagement — without leaving the chat. Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it. Nearby ## Other Productivity connectors ### [ChatData Sync](https://node8.ai/ai-connectors/productivity/chatdata-sync/) Builds private trackers from a plain English description ChatGPT ### [Floot](https://node8.ai/ai-connectors/productivity/floot/) Build, deploy, and host full-stack apps from chat ChatGPT ### [Folloze](https://node8.ai/ai-connectors/productivity/folloze/) Personalised B2B microsites and account journeys through Folloze Claude ### [3DOptix optical design and simulations](https://node8.ai/ai-connectors/productivity/3doptix-optical-design-and-simulations/) Optical system design with GPU ray tracing and irradiance analysis Claude ### [Agiflow](https://node8.ai/ai-connectors/productivity/agiflow/) Project and task tracking through chat commands ChatGPT ### [Aster Share](https://node8.ai/ai-connectors/productivity/aster-share/) Publish an HTML artifact as a private, expiring shareable link Claude [All 760 Productivity connectors](https://node8.ai/ai-connectors/productivity/) This is an independent catalogue entry compiled by Node8 from Docfarm's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Docfarm, and inclusion here is not an endorsement. ## Want your company reachable inside ChatGPT and Claude? Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot. [See how it works](https://node8.ai/mcp) Book a strategy session