MCP Things3 MCP Server

Most developer tooling work still happens through a UI a human drives. MCP Things3 MCP server moves it into the conversation instead. A robust MCP (Model Context Protocol) server providing comprehensive integration with Things3, allowing you to create, manage, and search tasks and projects through the MCP protocol. Features improved error handling, secure URL encoding.

The short version

• ✅ Create Projects: Create new projects in Things3 with full metadata support
• ✅ Create Todos: Create new to-dos with detailed properties including checklists, tags, and dates
• ✅ View Tasks: List tasks from inbox, today's list, or all projects
• ✅ Complete Tasks: Mark todos as completed by searching for their title
• ✅ Search Functionality: Search through all todos by title or content
• ✅ Robust Error Handling: Comprehensive validation and error recovery

The tools it exposes

The server publishes 4 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Components — The Components tool exposed by this server
• Debugging — The server includes comprehensive logging. Set log level for debugging:
• Contributing — 1. Fork the repository 2. Create a feature branch 3. Add tests for new functionality 4. Ensure all tests pass 5. Submit a pull request

What it needs from you

Configuration is passed through the environment: PYTHONPATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• macOS with Things3 installed - Python 3.8+ - Things3 running (for real-time operations)

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Things3's toolset — Prerequisites, Components, Debugging and 1 more — is a fair guide to whether it matches your workflow. It is maintained by drjforrest; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.