Things3 task management integration for macOS with comprehensive TODO, project, and tag management.
An MCP (Model Context Protocol) server that provides comprehensive integration with Things3 on macOS. This server enables AI assistants and other MCP clients to interact with Things3 through 25 specialized tools, offering complete task management capabilities with intelligent error correction and automatic tag creation.
You can use the server without any installation:
{
"mcpServers": {
"things3": {
"command": "npx",
"args": ["things3-mcp@latest"],
"env": {
"THINGS3_AUTH_TOKEN": "your_auth_token_here"
}
}
}
}
npm install -g things3-mcp
Then add to your MCP client configuration:
{
"mcpServers": {
"things3": {
"command": "things3-mcp",
"env": {
"THINGS3_AUTH_TOKEN": "your_auth_token_here"
}
}
}
}
# Clone the repository
git clone https://github.com/urbanogardun/things3-mcp.git
cd things3-mcp
# Install dependencies
npm install
# Build the project
npm run build
For update operations (modify, complete, delete), you need to set your Things3 authorization token:
export THINGS3_AUTH_TOKEN="your_auth_token_here"
To find your authorization token:
You can also create a .env
file (see .env.example
).
Open Claude Desktop configuration:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the Things3 MCP server using one of these methods:
Method 1: Using npx (easiest, no installation required)
{
"mcpServers": {
"things3": {
"command": "npx",
"args": ["things3-mcp@latest"],
"env": {
"THINGS3_AUTH_TOKEN": "your_auth_token_here"
}
}
}
}
Method 2: Global npm install
{
"mcpServers": {
"things3": {
"command": "things3-mcp",
"env": {
"THINGS3_AUTH_TOKEN": "your_auth_token_here"
}
}
}
Method 3: Local installation
{
"mcpServers": {
"things3": {
"command": "node",
"args": ["/absolute/path/to/things3-mcp/dist/index.js"]
}
}
}
Restart Claude Desktop
Use any of the methods above, adapting the configuration to your MCP client's format.
todos_list
List TODOs with flexible filtering options.
Parameters:
filter
: "inbox"
| "today"
| "upcoming"
| "anytime"
| "someday"
| "logbook"
(optional)searchText
: Search within titles and notes (optional)Example:
{
"filter": "today",
"searchText": "meeting"
}
todos_get
Get detailed information about a specific TODO.
Parameters:
id
: The TODO's unique identifier (required)todos_create
Create a new TODO with full property support (automatically creates tags if they don't exist).
Parameters:
title
: Task title (required)notes
: Additional notes (optional)whenDate
: ISO 8601 date string for scheduling (optional)deadline
: ISO 8601 date string for due date (optional)tags
: Array of tag names (optional)checklistItems
: Array of checklist item titles (optional) *projectId
: Assign to project (optional)areaId
: Assign to area (optional)heading
: Title of heading within project to add to (optional)Example:
{
"title": "Review Q4 Report",
"notes": "Focus on revenue metrics",
"whenDate": "2024-12-15T09:00:00Z",
"deadline": "2024-12-20T17:00:00Z",
"tags": ["work", "urgent"],
"checklistItems": ["Review revenue", "Check expenses", "Update forecast"],
"projectId": "project-id-here"
}
* Note on Checklists: When checklistItems
are provided, the TODO is created using Things3's URL scheme instead of AppleScript. This approach has some limitations:
todos_update
Update an existing TODO's properties (automatically creates tags if they don't exist).
Parameters:
id
: TODO identifier (required)todos_create
(optional)todos_complete
Mark one or more TODOs as complete.
Parameters:
ids
: Single ID or array of IDs (required)todos_uncomplete
Mark one or more TODOs as incomplete.
Parameters:
ids
: Single ID or array of IDs (required)todos_delete
Delete one or more TODOs permanently.
Parameters:
ids
: Single ID or array of IDs (required)projects_list
List projects with optional filtering.
Parameters:
areaId
: Filter by area (optional)includeCompleted
: Include completed projects (optional, default: false)projects_get
Get detailed project information.
Parameters:
id
: Project identifier (required)projects_create
Create a new project (automatically creates tags if they don't exist).
Parameters:
name
: Project name (required)notes
: Project description (optional)areaId
: Assign to area (optional)whenDate
: Start date (optional)deadline
: Due date (optional)tags
: Array of tag names (optional)headings
: Array of section headings (optional)projects_update
Update project properties (automatically creates tags if they don't exist).
Parameters:
id
: Project identifier (required)projects_create
except headings
(optional)projects_complete
Mark a project as complete.
Parameters:
id
: Project identifier (required)projects_delete
Delete projects completely from Things3.
Parameters:
ids
: Single project ID or array of project IDs (required)areas_list
List all areas.
Parameters:
includeHidden
: Include hidden areas (optional, default: false)areas_create
Create a new area.
Parameters:
name
: Area name (required)areas_delete
Delete areas completely from Things3.
Parameters:
ids
: Single area ID or array of area IDs (required)tags_list
List all tags with hierarchy information.
Returns: Array of tags with parentTagId
for nested tags
tags_create
Create a new tag.
Parameters:
name
: Tag name (required)parentTagId
: Parent tag for nesting (optional)tags_add
Add tags to items (automatically creates tags if they don't exist).
Parameters:
itemIds
: Single ID or array of TODO/Project IDs (required)tags
: Array of tag names to add (required)tags_remove
Remove tags from items.
Parameters:
itemIds
: Single ID or array of TODO/Project IDs (required)tags
: Array of tag names to remove (required)tags_delete
Delete tags completely from Things3.
Parameters:
names
: Single tag name or array of tag names (required)bulk_move
Move multiple TODOs to a project or area.
Parameters:
todoIds
: Array of TODO IDs (required)projectId
: Target project (optional)areaId
: Target area (optional)bulk_updateDates
Update dates for multiple TODOs.
Parameters:
todoIds
: Array of TODO IDs (required)whenDate
: New scheduled date or null to clear (optional)deadline
: New deadline or null to clear (optional)logbook_search
Search completed items in the logbook.
Parameters:
searchText
: Search in titles and notes (optional)fromDate
: Start date for range (optional)toDate
: End date for range (optional)limit
: Maximum results (optional, default: 50)system_launch
Ensure Things3 is running and ready.
The server automatically corrects common issues:
Human: Create a new project for the website redesign with tasks for planning, design, and implementation
Claude: I'll create a website redesign project with those tasks for you.
[Creates project and tasks using the Things3 MCP tools]
Create a TODO:
{
"tool": "todos_create",
"parameters": {
"title": "Prepare presentation",
"notes": "Include Q4 metrics and projections",
"whenDate": "2024-12-10T14:00:00Z",
"tags": ["work", "presentation"]
}
}
List today's tasks:
{
"tool": "todos_list",
"parameters": {
"filter": "today"
}
}
# Install dependencies
npm install
# Run in development mode with watch
npm run dev
# Run tests
npm test
# Run integration tests (requires Things3)
npm run test:integration
# Lint code
npm run lint
# Type check
npm run type-check
things3-mcp/
├── src/
│ ├── index.ts # Entry point
│ ├── server.ts # MCP server implementation
│ ├── config.ts # Configuration management
│ ├── tools/ # Tool implementations
│ │ ├── todos.ts # TODO operations
│ │ ├── projects.ts # Project operations
│ │ ├── areas.ts # Area operations
│ │ ├── tags.ts # Tag operations
│ │ ├── bulk.ts # Bulk operations
│ │ ├── logbook.ts # Logbook search
│ │ └── system.ts # System utilities
│ ├── templates/ # AppleScript templates
│ ├── utils/ # Utility functions
│ │ ├── applescript.ts # AppleScript bridge
│ │ ├── cache-manager.ts # Caching system
│ │ ├── error-correction.ts # Error correction
│ │ └── date-handler.ts # Date formatting
│ └── types/ # TypeScript definitions
├── tests/
│ ├── unit/ # Unit tests
│ └── integration/ # Integration tests
└── dist/ # Compiled JavaScript
osascript -e 'tell application "Things3" to return name of first to do'
npm run build
node dist/index.js
Contributions are welcome! Please follow conventional commit format and ensure all tests pass before submitting pull requests.