ClaudeListedTier: partner
Docfarm
Host, share, track and collaborate on anything you build with AI
First seen 2 Oct 2026. Evidence as of 2 Oct 2026.
25
Tools
From an anonymous probe
2
Source listings
Each with its own history
0
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| check_rebuild | Check a rebuild started by `rebuild_doc` and publish it when it is done. Returns the current stage while it is still building, so call it again after a pause. When the rebuild has finished this publishes it as a new HTML doc in the user's farm and returns the share link and the quality scores. Safe to call repeatedly: publishing twice returns the same doc. | Destructive |
| delete_doc | Permanently delete a doc the user OWNS — removes the document, its share link(s), all view/analytics data, chat, comments, suggestions, collaborators, and the stored file. IRREVERSIBLE. Only the owner can delete. Confirm with the user before calling if there's any ambiguity. Identify the doc via `doc_name` (fuzzy-matched) or `slug`. | Destructive |
| draft_followup | Viewing data for a doc to draft a follow-up email. | Read-only |
| duplicate_doc | Server-side copy of any HTML doc the user can read (their own OR shared with them) into their own farm under a new name. THE fast path for building a modified version of an existing doc: content never passes through your context — duplicate in ~1s, then use patch_doc for the differences. Vastly faster than get_doc_html + re-hosting. | Changes data |
| finalize_upload | FAST PATH step 2/2: after PUTting the file to the signed URL from `get_upload_url`, call this to publish. NEW name → new doc + share link. Name matching an EXISTING HTML doc → updated in place, same share link. Verifies the uploaded object exists before publishing. | Destructive |
| get_build_brief | READ THIS FIRST, before writing a single line of HTML for this user. Returns the docfarm house standard (how to pick the page archetype, type scale, spacing, logo rules, motion, budgets and language rules) plus this user's own brand: their colours, their typefaces, and asset tokens for their real logo and any font file they own. About 3,000 tokens and it is the difference between a page that looks like their company and a generic template. Write any asset token verbatim where the file goes (e.g. <img src="DF_ASSET_LOGO_1">), then pass the same doc name as `brand_from` on host_html_content and docfarm swaps in the real bytes. Never paste base64 yourself: the token is smaller, exact and free. Every page published to docfarm is scored against this standard on the way in, so reading it first is how you score well the first time instead of fixing afterwards. | Read-only |
| get_doc_html | Read the current HTML body of any docfarm HTML doc the user has access to — their own docs OR docs other people have shared with them (as collaborator or via share link). Returns title, share URL, the caller's role (owner / collaborator / reader), and the full HTML. ESSENTIAL precursor to `patch_doc`: call this first whenever the user asks for any change to a doc you don't have in context, so you can see what's there and construct accurate before/after snippets. Pass `doc_name` (easiest, fuzzy-matched) or `slug`. Embedded base64 images are stripped to placeholders by default (huge docs become readable in one call), so hosting a stripped copy back would drop those images from the doc; edit via patch_doc, or re-fetch with strip_data_uris: false for the byte-exact original. Large docs page via offset/max_chars — the response tells you the offset for the next slice. | Read-only |
| get_doc_status | Viewing stats for a doc. | Read-only |
| get_doc_url | Get a time-limited signed URL that downloads the raw file of any doc the user has access to — HTML, PDF, Markdown, anything stored on docfarm. Use this when you need to hand the file off to another tool or LLM, when the user asks for a download link, or when the doc isn't HTML (where get_doc_html doesn't apply). URL expires after `ttl_seconds` (default 3600, max 86400). | Read-only |
| get_share_link | Share URL for a doc. | Read-only |
| get_tracking_snippet | Tracking snippet for an HTML doc. | Read-only |
| get_upload_url | Step 1 of 2 for hosting a large HTML file that is already on disk, without sending its bytes through the model's context. Returns a short-lived signed upload URL; upload the file to it with a direct HTTP PUT (Content-Type: text/html), then call `finalize_upload` with the returned upload_path and a doc name. Requires a shell and unrestricted outbound HTTP, so the PUT will not succeed where outbound network access is restricted; `host_html_content` accepts the HTML inline and works in any environment. | Changes data |
| host_html_content | Host an HTML doc on docfarm and return its share link. A new name creates a new doc; a name matching an existing doc overwrites that doc in place, keeping its share link, password, and view stats, so anyone holding the URL sees the new version. Reuse the exact name to update a doc and change the name only to create a separate one. Takes the HTML inline, so it works in any environment. For a small change to an existing doc, `get_doc_html` + `patch_doc` sends far less content. Every page is scored against the docfarm house standard on the way in and the score comes back in the response; call `get_build_brief` BEFORE you write the HTML so you meet the standard first time rather than fixing afterwards. | Destructive |
| invite_collaborator | Invite someone to collaborate on a doc the user OWNS, by email, so it lands in their docfarm. If they're already a docfarm user the doc appears in their farm immediately; if not, they get an invite email with a signup link. REQUIRES the collaborator's `email` AND `allow_overwrite` (true = their edits overwrite the original; false = their edits fork into a copy they own, auto-shared back to the inviter). If you don't have the email, ask for it. If the user hasn't said whether the person should edit directly or only make a copy, ask before calling — don't guess. Identify the doc via `doc_name` (fuzzy-matched) or `slug`. | Destructive |
| list_accounts | List the farms this connection can reach: the signed-in account, plus the connected account when the person has one (docfarm's work/personal split, two separate farms held by one person). Call this FIRST whenever a request could concern either farm, or when the person says "my personal", "my work", "my other account", or names an address that is not the signed-in one. Then pass `account` on the tool you actually want. Docs, links, viewers and analytics never mix between the two. | Read-only |
| list_docs | List the docs the user OWNS in their docfarm. For docs other people have shared WITH the user, use `list_shared_with_me`. | Read-only |
| list_shared_with_me | HTML docs other docfarm users have added the caller to as a collaborator. Each entry also notes how patch_doc behaves (overwrite vs fork-on-edit) and points at any fork the caller already owns. | Read-only |
| patch_doc | Edit an existing hosted doc by replacing a snippet of its HTML. DEFAULT TOOL for ANY edit to a doc the user already has — typo, copy change, restyle, new section, anything. ~50 tokens instead of ~7000 for re-hosting. Workflow: (1) if you don't have the current HTML in context, call `get_doc_html` first to read it. (2) construct `before_snippet` as a unique chunk of the existing HTML and `after_snippet` as its replacement. Pass EITHER `doc_name` (easiest) OR `slug`. Ambiguous match → fails with context for each candidate. Preserves share link, password, view counts, comments. Patching sends only the changed snippet, so it costs far less than re-sending a whole doc, and `patch_doc_batch` covers even large rewrites. | Destructive |
| patch_doc_batch | Apply several patch_doc edits to one doc atomically — either all patches land or none do. Use for multi-region edits ("fix the typo AND change the CTA AND update the date") and for any change big enough to need multiple patches. Same workflow as patch_doc: call get_doc_html first if you don't have the HTML, then send a batch of before/after pairs. Identify the doc via `doc_name` or `slug`. | Destructive |
| propose_edit | Send a suggestion to the owner of a doc the user collaborates on, instead of changing the doc directly. Use mode "comment" to pass along free-form feedback for the owner to act on, or mode "fork" to copy the doc and apply a snippet edit in that copy. Use this when the user wants to suggest a change rather than make one; `patch_doc` is the tool for actually applying an edit. | Destructive |
| rebuild_doc | Rebuild a PDF or PowerPoint the user already has on docfarm into a live HTML page built to the house standard, keeping every fact and reorganising the layout so it reads on a phone. This is the retrofit: it does NOT reproduce the original layout, it rewrites the document into one of four archetypes. Takes about three minutes, so this tool STARTS the rebuild and returns immediately with a rebuild_id. Tell the user it is building, then call `check_rebuild` to collect it. PDF and PowerPoint only today. Before you start, ask the user whether they have another doc in their farm whose brand this should match, and pass it as `brand_from`. It is one question and it is the difference between their brand and a generic page, because an HTML doc in their farm usually carries the real logo file and sometimes the real typeface. Do not ask them how it should look: the shape of the page is decided from what the document is for. | Changes data |
| rename_doc | Rename a doc the user OWNS — changes its display title only. The share link/slug is intentionally left unchanged so existing recipients' URLs keep working. Identify the doc via `doc_name` (fuzzy-matched) or `slug`. | Destructive |
| track_html_page | Register a page the USER ALREADY HOSTS elsewhere (their website, Webflow, etc.) for visitor tracking — returns a script tag to paste into the page's <head>. Use `host_html_content` instead when docfarm should be the host. | Changes data |
| update_doc_settings | Update sharing settings for a doc the user OWNS: password protection (password_on / password_value), ask viewers for their name before viewing (ask_name), allow file downloads (allow_downloads), and view notifications for the owner (notify). Only the fields you pass are changed. | Destructive |
| whats_possible | Show a grouped overview of everything docfarm can do for the user — reading, editing, sharing, tracking, drafting follow-ups, and collaborating. Call this when the user asks 'what can you do?', 'what does docfarm do?', 'show me what's possible', 'help', or similar capability questions. Cheap and self-contained — no doc lookup needed. | Read-only |
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| claude.com listing page | 9fd0091d-88b7-46f3-a951-abeb9a8eb97c | 2 Oct 2026 | 2 Oct 2026 | 1 |
| MCPTop directory snapshot | anthropic:9fd0091d-88b7-46f3-a951-abeb9a8eb97c | 2 Oct 2026 | 2 Oct 2026 | 1 |