MustDo vs Planfix MCP — MCP Server Comparison | AllMCPs
MustDo vs Planfix MCP
A side-by-side look at the MustDo and Planfix MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MustDo for workplace & productivity work; choose Planfix MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
M
Choose MustDo when
You need dedicated capabilities in the Workplace & Productivity domain.
You have the keys it needs: MUSTDO_CK_API_TOKEN, MUSTDO_CK_ENV, MUSTDO_CK_CONTAINER, MUSTDO_CK_ZONE, MUSTDO_CALLBACK_PORT, MUSTDO_HOME, MUSTDO_LOG_LEVEL.
sign_inLocal only.** Opens Apple's sign-in page and stores `ckWebAuthToken`. Not present on the relay.
get_meAccount info: `timeZone`, `today`, `weekday`, `defaultTime`, `defaultDueNext`, trial/subscription dates, `canAddTodo`. Call this before doing date math.
list_todosLists To-Dos. Deleted ones are excluded. Repeating To-Dos are returned as **templates** under `repeating` (not expanded) with any per-day `occurrences` in range.
add_todoCreates a To-Do with `source = "mcp"`. **If `due` is omitted, it is tomorrow at the default time.
update_todoChanges only the fields you pass. `repeat` replaces the whole rule; `null` or `{ "kind": "none" }` removes it.
complete_todoOne-off: `status = done`. Repeating: marks that day's occurrence done (default: today).
snooze_todoSnoozes until `until`. Repeating: only that day's occurrence.
delete_todoSoft delete (`deletedAt`). The app purges it after 14 days.
Planfix MCP tools 20
get_tasksПолучить список задач из Planfix с пагинацией и фильтрами.
get_taskПолучить одну задачу по ID.
create_taskСоздать новую задачу в Planfix.
update_taskОбновить существующую задачу в Planfix (название, описание, статус, исполнитель).
get_contactsПолучить список контактов из Planfix с пагинацией и фильтрами.
get_contactПолучить одного контакта по ID.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MustDo
No confirmed install command for MustDo yet — follow the setup steps linked from its listing page rather than a guessed package name.
MustDo is categorized under Workplace & Productivity and uses an install path we have not confirmed yet. Planfix MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick MustDo for workplace & productivity work and Planfix MCP for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. MustDo has no confirmed install command yet — follow its own setup instructions.
MustDo is listed as free. Planfix MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mustdo and planfix-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MustDo has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Planfix MCP has 59/100 (Good) with 3 views, 0 installs and 4 GitHub stars.