Docferry: Share only one note

Share & showcase Plugins
, , ,
1

Disclaimer

Is this project open source? Yes, MIT license.
Is this project completely free? Yes. The plugin is free to install and DocFerry Cloud currently includes a free quota.
Is this project vibe-coded beyond the author’s ability to comprehend how it works? No. Docferry is developed and maintained by professional engineers.
Community Directory: DocFerry

Hi all! I built DocFerry for a straightforward sharing workflow I kept wanting in Obsidian:

Sometimes I do not want to publish a whole vault, folder, digital garden, or public site. I just want to send exactly one note to someone, keep the formatting readable, and be able to update or revoke that same link later.

DocFerry is a community plugin for that narrower workflow:

one selected note -> one secure share URL

image
image404×872 38.1 KB

What it does

Right-click a Markdown note and choose Share thru Docferry.

The publish dialog lets you:

  • confirm or edit the title
  • optionally add a password
  • choose no expiration or a 30-day expiration

After publishing, the share URL is copied for you.

Here is a live example reader page:

image
image1016×1476 171 KB

The reader view is meant to keep everyday note structure close to the source note. It supports common writing patterns such as callouts, Mermaid diagrams, tables, and image attachments. Referenced images and attachments can be shared together with the note in the same publish action, so you do not need to upload each attachment separately.

Updating the same link

If a note has already been published, the right-click menu changes. You can:

  • update the published content behind the same URL
  • copy the existing share link
  • check linked-note status
  • stop sharing

Stopping sharing revokes the link, so the URL no longer serves the note.

image
image399×1022 47 KB

Importing a shared note

DocFerry also has an import view. If someone sends you a DocFerry URL, you can paste it into the plugin view and import the shared note into your current vault as a local Markdown file. If the share is password-protected, the password prompt appears when needed.

What it intentionally does not do

DocFerry is not a full Obsidian Publish replacement. It does not publish an entire vault, folder, public directory, or digital garden.

It also does not automatically publish linked notes. If a shared note links to another note, that target note needs to be published separately before readers can open it through DocFerry.

I would especially appreciate feedback on:

  • Are there note elements that do not render well enough in the reader page?
  • Would you expect import to save assets in a different way?
  • whether the import workflow is clear enough for receiving shared notes from someone else?

Thank you all and happy ferrying!:ferry:

2 Likes
2

To get the latest release:

The Obsidian Community plugin directory can sometimes take a little time to reflect the newest GitHub release. If the Community Plugins browser is not showing the latest DocFerry version yet, you can install or update manually from GitHub.

Current latest GitHub release:
DocFerry 0.0.21

Stable latest-release link:

Manual install/update steps:

  1. Download the release assets manifest.json, main.js, and styles.css.
  2. Put them in your vault at .obsidian/plugins/docferry/.
  3. Restart Obsidian or reload the app.
  4. Enable DocFerry from Community Plugins if it is not already enabled.

This is only needed when you want the newest GitHub build before the plugin directory catches up. Otherwise, the normal Community Plugins install path is still the easiest option.:relieved_face: :ferry:

3

I wanted to know more about the background service, but…

image
image355×161 2.2 KB

Cheers, Marko :nerd_face:

4

Hi Marko, fair catch！

docferry.fuyonder.tech was set aside as the hosted service domain for free DocFerry share links, so I kept the root empty instead of treating it as a product landing page. :thinking:But yeah If someone opens the service domain directly, it should explain what the service is.

I will add a simple root/about page for docferry.fuyonder.techso people who open the service domain directly can see what it is, the privacy policy and terms,who is behind the project, etc.

Thanks for pointing out the rough edge!

5

Looks great! Small and simple. I :beating_heart: it!

Do you want that I bother you here or in GitHub? :slight_smile:

There is something small, half seen/hidden:

image

Cheers, Marko :nerd_face:

6

OK, after I tried with pass protected doc, it reviel more. So I guess only partial bug :slight_smile:

image

Cheers, Marko :nerd_face:

7

Forum is so much fun. Let’s talk here XD

Thank you so much for your feedback Marko!:laughing:

1 Like
8

Hmmm interesting. I can‘t reproduce the issue on my side. I’m actively looking into it.

1 Like
9

If I found it next time, you get info from DevTools. Now didn’t think about to gave you more on that …

Cheers, Marko :nerd_face:

10

DocFerry MCP: share and manage DocFerry links even when one side is not using Obsidian

Hi everyone, this is Rosetta the apple​:red_apple:

We have added DocFerry MCP:ship::trident_emblem:

The new MCP support is for a very specific collaboration gap: sometimes the person who wants to share something with me is not using Obsidian at all.:broken_chain:

They may be writing Markdown in VS Code, working in another editor, or using an AI assistant around a local project folder.

image
image1672×941 192 KB

In that case, that person can use an MCP-capable AI assistant to create or manage a DocFerry share from their own working environment. I can still receive a normal DocFerry link, and if I use Obsidian, I can import or manage DocFerry material from the plugin side.

The main use cases are:

  • Someone wants to share a Markdown document with me, but they are not an Obsidian user.
  • They may be using VS Code, another editor, or an AI assistant around a local folder.
  • They should not need to install Obsidian just to send one DocFerry link.
  • I can still receive, import, and manage DocFerry material from my Obsidian workflow.

image
image1672×941 211 KB

:red_apple::white_check_mark:Shares created or managed through MCP can still be reviewed from the DocFerry plugin panel in Obsidian.

So the MCP workflow is not a separate black box; Obsidian users can still keep visibility over their DocFerry shares from the familiar plugin surface.

Privacy note

If you use an AI assistant with MCP, please also check the privacy model of that MCP client and AI provider. DocFerry MCP gives the assistant a tool interface to DocFerry; it does not mean every AI automatically has access to your Obsidian vault.

MCP setup

https://docferry.fuyonder.tech/agent-kit/docferry-agent-kit-0.1.4.tar.gz

I would love feedback especially from people who receive Markdown documents from collaborators, clients, students, or friends who do not use Obsidian.

Thanks again to everyone who has tried DocFerry, reported rough edges, or encouraged the project.

11

:building_construction:Service restoration and feature update draft​:hammer_and_wrench:

DocFerry had a service interruption during a recent server migration. I am sorry for the disruption, especially if you tried to publish, import, sign in, or manage existing shares while the service was unavailable.

The hosted service has now been restored. The current public service domain is:

The current GitHub release is: DocFerry 0.0.75

Since the original showcase post, DocFerry has grown beyond the first single-note sharing release. The current plugin is still focused on Obsidian workflows, but now includes:

image
image1600×1000 44.9 KB

  • saving a public URL into your vault as a local Markdown link note;
  • importing a DocFerry Share back into Obsidian with its listed attachments;
  • publishing and managing one selected Markdown note as a stable Share URL;
  • password, expiration, update, stop, and inactive-history controls for Shares;
  • explicitly referenced local image and attachment handling;
  • linked-note availability inspection without automatically publishing linked notes;
  • optional Pro folder sharing for selected Markdown folders;
  • optional Pro theme styling for the responsive reader;
  • optional Advanced Import for enabled article, video, and audio sources after background processing.

If you are returning after the service interruption, I recommend updating to the latest Community Plugin version when it appears, or using the matching GitHub Release assets if you need the newest build before the Community Plugins browser catches up.

Thank you for the patience while I moved the service and cleaned up the release line.:light_blue_heart:

Rosetta