I am using Claude Cowork with both the NotePlan MCP and the Drafts MCP. Drafts plays a central role in many of the three dozen workflows that I’ve developed with Cowork. One example: I can assemble information in a draft and tag it with one of eight different tags that Cowork can identify. Cowork treats drafts differently based on the tag, creating the file needed in NotePlan and then filing it appropriately. The combination of these two MCPs and Cowork opens a lot of functional space.
5 Likes
Yeah, I’ve been using the Claude Cowork to create emails in drafts that I can quickly review and send to clients. This Drafts MCP works well.
The only thing that is missing is an ability to create and edit actions. There is already a Claude Drafts Action skill that works well, but I have to do a lot of copying and pasting to test out the actions and eventually it would be nice if claude could just do that for me.
I’ve created 39 different skills in Cowork in the last few weeks and many of them are dependent upon an interface with Drafts. A perfect marriage IMO.
1 Like
Drafts as a Multi-Purpose Interface
I was asked offline how I was using Drafts with Cowork. This is an evolving relationship – I keep finding more opportunities to use the Drafts MCP.
- Capture and Processing. I tag captured text to tell Cowork how to process it. I currently have six processing options, each identified by its own tag. Drafts are converted to a structured file with NotePlan tags, cross-folder connections, and review tasks with calculated dates – raw text in, structured files out.
- Extraction. I tag long-form sources (web articles, text OCR’d from PDFs) to tell Cowork to decompose them into one draft per idea and hold them for my review. When I approve a draft, it gets filed using the process described above.
- Job queue. I add Cowork prompts to tagged drafts – from my iPhone, for example – and Cowork executes them later in batch mode.
- Research briefs. I manage complex research tasks through a structured exchange between Drafts and Cowork: requirements go in, a draft document comes back, my revisions go in, an improved version comes back. The exchange repeats until I’m satisfied.
- Output. I receive Cowork deliverables, audit reports, and workflow execution reports in Drafts. I also use Drafts for progress snapshots – notes tagged to preserve session state during long multi-step tasks so work can resume accurately if the session is interrupted.
2 Likes
Quick update. Drafts is central to about 1/3 of the 48 methods (aka skills) and 10 technical references that I’ve created with Cowork over the past several weeks. But, the methods that depend on Drafts are more frequently used than most of the others. It is likely that over half of all methods I invoke are dependent upon Drafts. If Drafts disappeared I would have to start over with Cowork and I’m not sure how far I would get.
Hey Im interested in starting to use Drafts as a way to conduct Claude.
@Bjb Can i ask how you have set claude up to listen for drafts (applying tags)? Or is it more that you have an drafts actions that applies a tag and tells claude to do something?
Also interested in how you manage a large volume of drafts or do you archive most of them once finished?
cheers
I continue to use Drafts much as I did before, but have a new “customer” for it - the NotePlan folder that is designed for use by Cowork. To avoid the overhead token costs associated with MCPs (NotePlan’s and Drafts’) I move drafts to NotePlan using a Drafts Action and from NotePlan to Drafts using a Keyboard Maestro macro.
When I send a draft to NotePlan (for Cowork to process) it is tagged in a manner that instructs Cowork what to do with it.
I archive drafts that are no longer “in play”.