Things 3 MCP servers: local and remote options
Things 3 has community MCP servers for Mac and remote access. Compare local integrations, unofficial Things Cloud bridges, and Done Bear's hosted MCP.
Short answer: Things 3 has community MCP servers, including projects with remote access. Cultured Code does not offer a direct AI integration. The useful distinction is how a server accesses your tasks, who maintains it, and what needs to stay running.
If you want to keep using Things, inspect the community options below. If you want Windows, web, shared lists and an MCP server maintained by the task app’s developer, Done Bear is another option.
Is there an official Things 3 MCP server?
Cultured Code’s guidance on third-party AI tools says it does not offer direct integrations with Claude, ChatGPT or coding agents. It acknowledges community MCP servers and identifies the URL scheme, Apple Shortcuts, AppleScript and Mail to Things as supported integration methods.
That is different from saying an AI assistant cannot use Things. Community projects provide that connection, with different approaches to reading and changing your list.
Which kind of Things MCP server fits your setup?
| Approach | Where it runs | What to check |
|---|---|---|
| Local Mac integration | On the Mac with Things | Read and write methods, macOS permissions, supported fields |
| Mac integration with HTTP transport | On a reachable Mac | Authentication, client compatibility, and whether the Mac stays available |
| Unofficial Things Cloud bridge | On a server you operate | Unsupported sync access and Cultured Code’s warning about Cloud credentials |
| Done Bear hosted MCP | On Done Bear’s service | Uses a Done Bear account and task list; moving from Things requires an import |
Remote access is possible in more than one way. It does not by itself establish that a server uses a supported Things integration.
Local servers for Claude Desktop and coding agents
For example, than/things-mcp describes SQLite reads with an AppleScript fallback and writes through the Things URL scheme. It runs on macOS. Its README explains the permissions required by each backend and which fields the fallback can read.
Review the actual backend before connecting. Reading a local database and changing it directly are different operations. Cultured Code explicitly warns against direct database writes; its published list of supported methods is the starting point for evaluating an integration.
A local server can be useful if your existing Things workflow fits and your assistant runs on the same Mac. Check the project’s installation instructions and limitations against the client you use.
Can a Things MCP server work remotely?
Yes. piersdd/things-3-mcp documents HTTP transport with authentication around a Mac-based integration. That repository was archived on April 5, 2026, so it illustrates the approach rather than serving as a maintained installation recommendation. The Mac and server still need to be available.
There are also projects that bypass the Mac. things-cloud-mcp describes a server that connects to Things Cloud through a reverse-engineered SDK and exposes an MCP endpoint. These are the project’s documented capabilities; we have not independently tested it.
Cultured Code warns against tools that request Things Cloud credentials because unsupported access can cause data loss. The existence of a remote bridge does not make it an official or recommended connection. Check transport and authentication support in your chosen assistant, too.
When Done Bear’s hosted MCP makes sense
Done Bear hosts an MCP server at https://mcp.donebear.com/mcp. Follow the setup guide for Claude, ChatGPT, Cursor, or Claude Code to connect your account with OAuth.
The assistant can read tasks, add tasks, triage the inbox and complete work in Done Bear. Review the tool permissions in your client; approval behavior depends on that client’s settings. Your Mac does not need to run a Things bridge.
Done Bear maintains this server for its own task model. It is not a two-way Things sync service. The MCP documentation describes the available tools.
Keep Things if its Apple apps and personal workflow meet your needs. Consider Done Bear if you also need Windows, the web app, or a list shared with other people and agents.
Moving your tasks from Things
Start free and open the Things importer. On the Mac with Things, make a copy of its main.sqlite database, then upload that copy. Review the import preview before confirming.
If you prefer the command line, the Things import guide covers donebear import things, including its dry-run option. Keep your original Things list while you check the imported tasks.
Done Bear is free up to 250 tasks with no credit card. Try the import and one real task before deciding whether to move the rest of your workflow.
Start free with agent access
The same list your CLI and Claude already use. Free up to 250 tasks. No credit card.
Get new posts by email
New writing on GTD, local-first software, and building a calm task manager, sent when it is published. Nothing else, and you can leave any time.