This Model Context Protocol (MCP) server lets you use Claude Desktop to interact with your task management data in Things app. You can ask Claude to create tasks, analyze projects, help manage priorities, and more.
This server leverages the Things.py library and the Things URL Scheme, with additional reliability features including:
- Robust error handling with exponential backoff and retry mechanisms
- Circuit breaker pattern to prevent cascading failures
- Dead letter queue for failed operations
- Intelligent caching for improved performance
- Comprehensive logging with structured JSON output
- AppleScript bridge for operations that fail with URL schemes
- Rate limiting to prevent overwhelming the Things app
- Extensive test suite for reliability
This MCP server unlocks the power of AI for your task management:
- Natural Language Task Creation: Ask Claude to create tasks with all details in natural language
- Smart Task Analysis: Get insights into your projects and productivity patterns
- GTD & Productivity Workflows: Let Claude help you implement productivity systems
- Seamless Integration: Works directly with your existing Things 3 data
- Access to all major Things lists (Inbox, Today, Upcoming, etc.)
- Project and area management
- Tag operations
- Advanced search capabilities
- Recent items tracking
- Detailed item information including checklists
- Support for nested data (projects within areas, todos within projects)
There are multiple ways to install and use the Things MCP server:
- Python 3.12+
- Claude Desktop
- Things 3 ("Enable Things URLs" must be turned on in Settings -> General)
- Things Authentication Token (required for URL scheme operations)
pip install things-mcp
Or using uv (recommended):
uv pip install things-mcp
After installation, you can run the server directly:
things-mcp
- Python 3.12+
- Claude Desktop
- Things 3 ("Enable Things URLs" must be turned on in Settings -> General)
Install uv if you haven't already:
curl -LsSf https://astral.sh/uv/install.sh | sh
Restart your terminal afterwards.
git clone https://github.com/hald/things-mcp
cd things-mcp
uv venv
uv pip install -r pyproject.toml
Run the configuration tool to set up your Things authentication token:
python configure_token.py
This will guide you through the process of configuring your Things authentication token, which is required for the MCP server to interact with your Things app.
Edit the Claude Desktop configuration file:
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
Add the Things server to the mcpServers key in the configuration file (be sure to update the path to the folder where you installed these files):
{
"mcpServers": {
"things": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/things-mcp",
"run",
"things_server.py"
]
}
}
}
The Things URL scheme requires an authentication token. You can find it in Things → Settings → General.
Option 1: Set via configuration script
python configure_token.py
Option 2: Set via environment variable
export THINGS_AUTH_TOKEN="your-token-here"
Option 3: Manually create config file
mkdir -p ~/.things-mcp
echo '{"things_auth_token": "your-token-here"}' > ~/.things-mcp/config.json
Restart the Claude Desktop app to apply the changes.
- "What's on my todo list today?"
- "Create a todo to pack for my beach vacation next week, include a packling checklist."
- "Evaluate my current todos using the Eisenhower matrix."
- "Help me conduct a GTD-style weekly review using Things."
- Create a project in Claude with custom instructions that explains how you use Things and organize areas, projects, tags, etc. Tell Claude what information you want included when it creates a new task (eg asking it to include relevant details in the task description might be helpful).
- Try adding another MCP server that gives Claude access to your calendar. This will let you ask Claude to block time on your calendar for specific tasks, create todos from upcoming calendar events (eg prep for a meeting), etc.
get-inbox
- Get todos from Inboxget-today
- Get todos due todayget-upcoming
- Get upcoming todosget-anytime
- Get todos from Anytime listget-someday
- Get todos from Someday listget-logbook
- Get completed todosget-trash
- Get trashed todos
get-todos
- Get todos, optionally filtered by projectget-projects
- Get all projectsget-areas
- Get all areas
get-tags
- Get all tagsget-tagged-items
- Get items with a specific tag
search-todos
- Simple search by title/notessearch-advanced
- Advanced search with multiple filters
get-recent
- Get recently created items
add-todo
- Create a new todo with full parameter supportadd-project
- Create a new project with tags and todosupdate-todo
- Update an existing todoupdate-project
- Update an existing projectdelete-todo
- Delete a todo (moves to trash)delete-project
- Delete a project (moves to trash)show-item
- Show a specific item or list in Thingssearch-items
- Search for items in Things
project_uuid
(optional) - Filter todos by projectinclude_items
(optional, default: true) - Include checklist items
include_items
(optional, default: false) - Include contained items
status
- Filter by status (incomplete/completed/canceled)start_date
- Filter by start date (YYYY-MM-DD)deadline
- Filter by deadline (YYYY-MM-DD)tag
- Filter by tagarea
- Filter by area UUIDtype
- Filter by item type (to-do/project/heading)
period
- Time period (e.g., '3d', '1w', '2m', '1y')
title
- Title of the todonotes
(optional) - Notes for the todowhen
(optional) - When to schedule the todo (today, tomorrow, evening, anytime, someday, or YYYY-MM-DD)deadline
(optional) - Deadline for the todo (YYYY-MM-DD)tags
(optional) - Tags to apply to the todolist_title
orlist_id
(optional) - Title or ID of project/area to add toheading
(optional) - Heading to add underchecklist_items
(optional) - Checklist items to add
id
- ID of the todo to updatetitle
(optional) - New titlenotes
(optional) - New noteswhen
(optional) - New scheduledeadline
(optional) - New deadlinetags
(optional) - New tagscompleted
(optional) - Mark as completedcanceled
(optional) - Mark as canceled
title
- Title of the projectnotes
(optional) - Notes for the projectwhen
(optional) - When to schedule the projectdeadline
(optional) - Deadline for the projecttags
(optional) - Tags to apply to the projectarea_title
orarea_id
(optional) - Title or ID of area to add totodos
(optional) - Initial todos to create in the project
id
- ID of the project to updatetitle
(optional) - New titlenotes
(optional) - New noteswhen
(optional) - New scheduledeadline
(optional) - New deadlinetags
(optional) - New tagscompleted
(optional) - Mark as completedcanceled
(optional) - Mark as canceled
id
- ID of the todo to delete (moves to trash)
id
- ID of the project to delete (moves to trash)
id
- ID of item to show, or one of: inbox, today, upcoming, anytime, someday, logbookquery
(optional) - Optional query to filter byfilter_tags
(optional) - Optional tags to filter by
- Tags must exist in Things before they can be applied to todos or projects
- The MCP server will automatically create missing tags when you try to use them
- If tag creation fails, the todo/project will still be created but without tags
- Required for all URL scheme operations (create, update, delete)
- Without a token, Things will prompt for authentication on each operation
The Things MCP server requires an authentication token to interact with the Things app. This token is used to authorize URL scheme commands.
- Open Things app on your Mac
- Go to Things → Preferences (⌘,)
- Select the General tab
- Make sure "Enable Things URLs" is checked
- Look for the authentication token displayed in the preferences window
Run the included configuration tool to set up your token:
python configure_token.py
This interactive script will prompt you for your token and save it securely in your local configuration.
This project uses pyproject.toml
to manage dependencies and build configuration. It's built using the Model Context Protocol, which allows Claude to securely access tools and data.
This project provides two different implementation approaches:
-
Standard MCP Server (
things_server.py
) - The original implementation that uses the basic MCP server pattern. -
FastMCP Server (
things_fast_server.py
) - A modern implementation using the FastMCP pattern for cleaner, more maintainable code with decorator-based tool registration.
# Clone the repository
git clone https://github.com/hald/things-mcp
cd things-mcp
# Set up a virtual environment with development dependencies
uv venv
uv pip install -e ".[dev]" # Install in development mode with extra dependencies
Use the MCP development server to test changes:
# Test the FastMCP implementation
mcp dev things_fast_server.py
# Or test the traditional implementation
mcp dev things_server.py
python -m build
twine upload dist/*
Requires Python 3.12+.
- Retry Logic: Automatic retries with exponential backoff for transient failures
- Circuit Breaker: Prevents repeated failures from overwhelming the system
- Dead Letter Queue: Failed operations are stored for later retry or analysis
- AppleScript Fallback: When URL scheme operations fail, falls back to direct AppleScript
- Smart Caching: Frequently accessed data is cached with appropriate TTLs
- Rate Limiting: Prevents overwhelming Things app with too many requests
- Cache Invalidation: Automatic cache clearing when data is modified
- Structured Logging: JSON-formatted logs for better analysis
- Operation Tracking: Each operation is logged with timing and status
- Cache Statistics: Monitor cache performance with
get-cache-stats
tool - Log Locations:
- Main logs:
~/.things-mcp/logs/things_mcp.log
- Structured logs:
~/.things-mcp/logs/things_mcp_structured.json
- Error logs:
~/.things-mcp/logs/things_mcp_errors.log
- Main logs:
The server includes error handling for:
- Invalid UUIDs
- Missing required parameters
- Things database access errors
- Data formatting errors
- Authentication token issues
- Network timeouts
- AppleScript execution failures
- Missing or invalid token: Run
python configure_token.py
to set up your token - Things app not running: The server will attempt to launch Things automatically
- URL scheme not enabled: Check that "Enable Things URLs" is enabled in Things → Preferences → General
- Operations failing: Check the circuit breaker status and dead letter queue
- Performance issues: Monitor cache statistics with the
get-cache-stats
tool
All errors are logged and returned with descriptive messages. To review the MCP logs:
# Follow main logs in real-time
tail -f ~/.things-mcp/logs/things_mcp.log
# Check error logs
tail -f ~/.things-mcp/logs/things_mcp_errors.log
# View structured logs for analysis
cat ~/.things-mcp/logs/things_mcp_structured.json | jq
# Claude Desktop MCP logs
tail -n 20 -f ~/Library/Logs/Claude/mcp*.log
- Check Dead Letter Queue: Failed operations are stored in
things_dlq.json
- Monitor Circuit Breaker: Look for "Circuit breaker" messages in logs
- Cache Performance: Use
get-cache-stats
tool to check hit rates - Enable Debug Logging: Set console level to DEBUG in
logging_config.py