The Two Ways In: Cloud API and MCP

The Two Ways In: Cloud API and MCP An architecture diagram generated by Archify. AI assistant · Claude, ChatGPT, others · Architecture component AI assistant Claude, ChatGPT, others MCP server · tools for tasks and projects · Architecture component MCP server tools for tasks and projects @mindwtr/core · the same rules as the apps · Architecture component @mindwtr/core the same rules as the apps Mindwtr apps · desktop and phone · Architecture component Mindwtr apps desktop and phone Bearer token · one data set per token · Architecture component · Authorization header Bearer token one data set per token Authorization header Health check · GET /health · Mindwtr Cloud, the server you host Health check GET /health Sync document · /v1/data · Mindwtr Cloud, the server you host · server merges Sync document /v1/data server merges Records · tasks, projects, areas · Mindwtr Cloud, the server you host · and search Records tasks, projects, areas and search Attachments · /v1/attachments · Mindwtr Cloud, the server you host Attachments /v1/attachments Calendar feed · /v1/calendar · Mindwtr Cloud, the server you host Calendar feed /v1/calendar asks in plain words reads and writes or a cloud address instead every call carries a token no token needed Mindwtr Cloud, the server you host

The cloud API

  • • Every path under /v1 needs a bearer token. The token names the data set it may touch.
  • • Sending the whole document to /v1/data is not an overwrite. The server merges it in.
  • • Records covers tasks, projects, sections and areas, plus a search endpoint over tasks and projects.

The MCP server

  • • MCP is the Model Context Protocol. It lets an assistant call tools instead of clicking the app.
  • • There is one tool per action: add, get, list, change, delete, complete and restore.
  • • By default it reads the local database. Pointed at a cloud address it stays read-only until you allow writes.

One set of rules

  • • Both doors run the same core package, so quick-add text and validation behave the same everywhere.
  • • The calendar feed is the one exception: the token sits in the link, so a calendar app can read it.
  • • The attachment endpoints also clean up files the document no longer refers to.