← Back to research
·8 min read·company

Drafts

Drafts is an Apple-platform text capture app with actions, scripting, MCP, and a new AI console. Review its free tier, storage model, automation boundaries, and workflows.

Key takeaways

  • Drafts separates capturing text from deciding which app or workflow should receive it.
  • Free includes capture, synchronization, and running installed actions; Pro adds custom actions, workspaces, and other advanced features.
  • The library syncs through CloudKit rather than a folder of Markdown files, so export and backup deserve separate evaluation.
  • Mac MCP access and the Drafts 54 Chat Console are different automation surfaces with different requirements.

FAQ

Is Drafts free?

The core capture, editing, sync, and installed-action workflow is free. Pro is $1.99 per month or $19.99 per year in the US, with advanced organization and automation features.

Does Drafts store ordinary Markdown files in a folder?

Its library uses application-managed storage and CloudKit sync. Actions can export text to files, but the live library is not an iCloud Drive Markdown vault.

Can an AI agent use Drafts?

The official Mac MCP server exposes search, creation, updates, and action execution through AppleScript. Drafts 54 also includes a separate Pro Chat Console, requiring Apple Intelligence and macOS or iOS 27 or later.

Does Pro include paid model usage?

No. The console can use supported Apple models, while external providers require the user's own API credentials and billing. Processing location depends on the selected model.

Executive Summary

Drafts is a text capture and automation app from Agile Tortoise for Mac, iPhone, iPad, and Apple Watch. It starts with an editor, then lets the user decide where the text should go. Actions can transform that text or route it to another application or service.[1][2]

Its place in the minimalist Markdown Mac notes comparison is quick capture with an unusually extensible exit path. It can serve as a writing library, but its storage model differs from an ordinary folder of Markdown files: the application manages the library and synchronizes it through CloudKit.[3] That distinction matters for people who want agents, scripts, and multiple editors to work directly on the same files.

AttributeCurrent position
DeveloperAgile Tortoise[4]
PlatformsMac, iPhone, iPad, Apple Watch[1]
Core workflowCapture text, organize it, run an action[5]
Commercial modelFree core; optional Pro subscription[6]

Product Overview

The application has three main parts: the editor, the draft library, and actions. The editor works with plain text and syntax highlighting, including Markdown. The library adds tags, search, flags, an inbox, and an archive. Actions provide the output and transformation layer.[5][7]

This separation supports a practical habit: capture a thought immediately, then decide later whether it belongs in a note, task, email, or publication. It also creates a responsibility. Without a processing routine, the inbox can become another place to lose unfinished work.

A concrete capture-to-file workflow

A useful evaluation is to capture a short note on the device used most often, tag it, and find it again on the Mac. Run an installed action that exports or routes the text to its intended destination. Inspect the resulting file or draft before adding more automation. The action system supports multiple steps and can invoke services or scripts; custom action editing requires Pro.[2][6]

Then edit the original and repeat the action. Does the workflow append, overwrite, or create a duplicate? That is a property of the selected action, not a general promise made by Drafts. Test the actual destination and naming behavior before making it the only path into a permanent collection.

For organization, first try tags and the built-in inbox/archive views. Pro workspaces become useful when repeated filtering deserves its own saved context.[7][6] These are proposed evaluation steps, not a claim that this review installed and exercised the application.


Storage, Sync, and Recovery

Drafts synchronizes notes, version history, actions, workspaces, settings, and other application state through iCloud. Devices use the same iCloud account. CloudKit sync is not file sync: the live notes do not appear as editable Markdown documents in iCloud Drive.[3] Exporting files can connect Drafts to a folder-based workflow, but does not turn the library into a shared filesystem vault.

Separate history from backup

Version history helps recover a prior draft; Trash retains deleted drafts for 30 days. For broader recovery, Drafts supports on-demand and periodic backups. Note backups use a JSON-based .draftsExport format. Restoring offers a choice between updating matching records and importing new records, so the selected option affects duplication.[8]

The backup guide also distinguishes current cloud state from a historical backup. Periodic backup timing depends on launching and using the application. A useful evaluation includes opening an exported backup and practicing recovery with disposable notes, rather than assuming that successful synchronization proves every recovery scenario works.[8]

Encryption has a defined scope

Drafts 52 added support for Apple's Advanced Data Protection. When ADP is enabled, supported content fields use end-to-end encryption; this does not cover every metadata or settings field. Older content and history require the documented migration process to receive the new protection. Enabling a cloud account alone is not equivalent to enabling ADP.[9]


Automation and AI

Actions and Mac agent access

Actions can be installed from the community directory and run on the free tier. Pro adds creating and editing actions, including workflows with script steps.[2][6] Treat the action's destination and permissions as part of its behavior: text sent to an external service is no longer governed solely by local storage choices.

The official MCP server uses AppleScript to control the Mac app. It exposes draft search, creation, updates, tags, status changes, and action execution. The same package includes a drafts CLI with machine-readable JSON output. Its published requirements include macOS, Drafts 50.0.3 or later, and Node.js 18 or later.[10]

This is meaningful write access, not just retrieval. An agent can change drafts and run actions whose effects extend beyond the library. Evaluate the MCP client's approval settings and the actions available to it before connecting a valuable collection. The reviewed README does not establish a universal read-only boundary.[10]

Drafts 54 Chat Console

The separate in-app console requires Pro, Apple Intelligence, and macOS or iOS 27 or later. Optional tools cover the editor, library, history, files, reminders, and calendars.[11]

Model choices include on-device Apple inference, Private Cloud Compute, and external providers using separately billed API credentials. Sessions are temporary, without persistent chat history.[11] These console requirements do not apply to every existing Drafts feature. Choose the model and tools according to the data involved; local note storage alone does not determine processing location.


Strengths and Cautions

StrengthCorresponding tradeoff
Capture before organizationA simple input surface still benefits from a deliberate processing habit[5]
Actions connect many destinationsCustom workflows introduce configuration and maintenance work[2]
Free includes a useful daily workflowWorkspaces and custom action editing are Pro features[6]
Library state travels across Apple devicesThe live collection is not a folder that any editor can modify[3]
MCP and CLI expose real operationsAgent access can modify content and invoke consequential actions[10]

What Users Say

In a 2026 r/macapps account, Downtown-Art2865 described using Drafts as a capture inbox before routing material to Obsidian, email, and task workflows. The author explicitly reported paying for Pro and having no affiliation. Their useful observation was organizational: postponing the destination decision made capture easier.[12]

The same user reported a 2024 sync incident, a learning curve for JavaScript actions, and maintenance work after operating-system changes. These are dated, individual experiences, not measured failure rates or proof of a current sync defect. They support testing recovery and starting with a small action set rather than equating an extensible app with a maintenance-free workflow.[12]


Pricing & Licensing

US pricing checked September 15, 2026:[6]

PlanPriceScope
Free$0Capture, editing, sync, and running installed actions
Pro monthly$1.99/monthCustom actions, workspaces, and advanced features
Pro annual$19.99/yearSame Pro entitlement; seven-day trial offered

Pro spans the supported Apple platforms through the documented account-sharing mechanism.[3] Paid external model usage is additional.[11] The product is a commercial application; availability of an official MCP repository does not make the entire app open source.


Competitive Positioning

The important choice is the job assigned to the app. Evaluate Drafts for capturing and routing text. Evaluate Obsidian, FSNotes, or iA Writer when the central requirement is working on a durable collection of documents. These can be complementary roles rather than a forced replacement decision.

Drafts is especially relevant when the same raw text repeatedly becomes several different outputs. It is less compelling when the desired workflow is simply to open an existing Markdown file, edit it, and save it in place. The category comparison separates capture tools from file editors and library-oriented notes apps.


Viability Assessment

The current App Store history includes Drafts 54 and its Chat Console, following releases that added colored flags and ADP support. That establishes ongoing product development through September 2026.[4] It does not establish a guaranteed future roadmap. The durable evaluation criteria are whether capture and routing save time, whether exported content remains usable, and whether recovery is understood.

Recommended for: Apple-platform users who repeatedly capture text before deciding its destination, particularly those willing to build a small set of reusable actions.

Poor fit: A requirement for a live filesystem vault, or a team workflow centered on shared document editing.


Research by Ry Walker Research • methodology