drafts

The Drafts MCP Server exposes a set of MCP-compliant commands that let an AI assistant interact with the Drafts app on macOS through AppleScript. Once running via npx or a local install, you can query, create, update, and search drafts, manage tags, workspaces, and run Drafts actions from your AI workflow. The server supports workspace listing, draft CRUD operations, search, tagging, and action execution, enabling automation scenarios like fetching drafts from a particular workspace, creating drafts from chat summaries, or applying tags and flags in bulk. Typical use involves sending structured MCP requests to the server’s endpoints and receiving JSON responses that reflect the Drafts data and operation results.

Available capabilities include:

• Workspace management: list and query workspaces
• Draft operations: create, get, update, and search drafts with flexible filtering (content, folder, tag, flags, dates)
• Tag management: add tags to drafts
• Actions: list and run Drafts actions on specific drafts
• Draft status: flag, archive, or trash drafts All interactions are designed to be language-agnostic, so you can drive them from Claude, Cursor, or your own automation scripts.

Prerequisites:

• macOS with AppleScript support
• Node.js 18 or higher installed on your Mac
• Drafts app (v50.0.3 or greater) installed

Install options:

1. Quick start (no local install required):

• Ensure Node is installed (you may use Homebrew):

brew install node

• Run the MCP server via npx (no local install needed):

npx @agiletortoise/drafts-mcp-server

2. Global installation (optional, for local access):

npm install -g @agiletortoise/drafts-mcp-server

Then run with:

drafts-mcp-server

3. Local development/testing (from repository clone):

# Clone the repository
git clone https://github.com/agiletortoise/drafts-mcp-server.git
cd drafts-mcp-server

# Install dependencies
npm install

# Build (if applicable)
npm run build

# Test with MCP Inspector
npm run inspector

# Or run directly from built output
node dist/index.js

Tips and caveats:

• macOS permissions: The first run will prompt for Automation permissions to allow the MCP host (Claude Desktop, Claude Code, Cursor, etc.) to control Drafts. Grant the permissions in System Settings > Privacy > Automation.
• If you use Claude Desktop or Claude Code, you can configure the server in Claude’s settings by pointing to npx @agiletortoise/drafts-mcp-server or to a local node path when developing locally.
• Environment variables are not strictly required for basic operation; if you run in constrained environments, you may need to ensure Node can access Drafts and that the MCP host has automation privileges.
• The npm package name to reference in MCP configurations is @agiletortoise/drafts-mcp-server. When testing locally, you can load the built dist/index.js file via node for direct operation.
• For debugging, you can use the MCP Inspector script (npm run inspector) to verify MCP payloads and responses before integrating into an AI workflow.