Things Orchestrator for developers and agents

Things Orchestrator is an unofficial, self-hosted MCP server for one Things Cloud account.

Use it when

Use Things Orchestrator when a person wants an MCP client to read or change their Things 3 data while Things stays the system of record. It is a fit for a Mac, a private Linux server reached through Tailscale, or a public HTTPS host that the user controls.

Do not use it as a multi-tenant service, a general Things Cloud API, or a replacement for Things. Do not send a Things Cloud password to an agent. The password belongs only on the serving host.

Agent interface

The version 0.9.0 MCP server exposes eight tools: things_view, things_find, things_get, things_capture, things_update, things_complete, things_trash, and things_receipt. The HTTP service uses Streamable HTTP transport at the /mcp path of the user's own host.

Every mutation needs a fresh UUID or ULID request ID. A client may reuse that ID only to retry the exact same transport request. The server freezes the operation, reads Things Cloud back, and returns an immutable receipt. A pending result blocks further writes until the client retries that same request for reconciliation. A partial result is terminal.

Install and integrate

Install an exact Git tag with uv, sign in on the serving host, install the supervised service, and run things-orchestrator doctor --wait. Then run things-orchestrator print-config --client <name> to produce the configuration for Claude Code, Codex, Cursor, Hermes, or another MCP client.

The public repository contains the full install guide, client-specific configuration, operations guide, trust notes, security policy, source, and tests. The agent skill published on this domain is a copy of the skill bundled with version 0.9.0.