Mizito MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIZITO_TOKEN | Yes | Mizito session token, written to .env by refresh-auth.sh or pasted by hand. Never expose, log or commit it. | |
| MIZITO_PYTHON | No | Python interpreter to use (default .venv/bin/python, else python3). | |
| MIZITO_ENV_FILE | No | Path to another env file (for example one per workspace or account). Not needed when MIZITO_TOKEN is already in the environment. | |
| MIZITO_CACHE_TTL | No | Seconds that users, projects, labels and chats stay cached. | 300 |
| MIZITO_LOG_LEVEL | No | Log level, e.g. INFO. Logs one stderr line per API call, never with bodies or the token. | |
| MIZITO_READ_ONLY | No | Set to 1 to disable all write tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Mizito (office.mizito.ir) is the team's project-management + chat tool: projects with kanban boards, tasks, task comments, and team chat.
How to use these tools well:
Start cheap: daily_brief or get_projects_summary answer most status questions in one call. list_tasks is the main task query (filters by project, board, assignee, label, status, overdue, text).
Arguments named user/assignee/project/board/label/chat accept an id OR a name/title. Persian names match even with Arabic ي/ك or ZWNJ differences. "me" means the current user. Ambiguous names raise an error listing the candidates: pick one and pass its id.
Task ids come from list_tasks/search_tasks. Checklist item ids and comment ids come from get_task.
Dates: results carry UTC ISO plus *_fa = Tehran time on the Jalali calendar. Inputs accept "YYYY-MM-DD HH:MM" (Gregorian, Tehran time), "1405/08/30 14:00" (Jalali) or ISO with Z.
"When is it due" = the reminder (reminder/reminder_fa; set_task_reminder): that is what Mizito uses for today / overdue.
deadline("مهلت انجام") exists only in projects with the deadline feature.Write tools change real shared data that teammates see and get notified about. Confirm with the user before writing unless they asked for that exact change. Every write reads the object back and reports the verified result; if a write tool raises, treat the change as NOT done and check with a read before retrying.
Chat messages are often task cards (type=task_card) with empty text: report the task title instead of calling the message empty.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Current user and workspace: ids, name, role, plan days left, storage. Call first when you need your own user id (it appears as owner / assignee / message sender elsewhere). |
| list_workspace_usersA | Members of the current workspace: id, name, role, online/last seen, and what each one last worked on.
|
| list_workspacesA | Every workspace this account belongs to, with unread chat/inbox and
task counts per workspace. |
| switch_workspaceA | Point every tool at another workspace (id or title from list_workspaces) for the rest of this MCP session. Mizito binds a workspace to the token: |
| get_dashboard_summaryA | Raw cross-workspace rollup (unread + task buckets). Prefer list_workspaces, which is the same data, cleaned up. |
| get_task_countsA | My task badge counts in this workspace: due today and total open. |
| health_checkA | Check the Mizito connection: token accepted, workspace, latency. Use when other tools fail, before telling the user Mizito is down. |
| list_projectsA | Projects in the workspace with boards, admins, chat id and (by default) task counts: total / done / open / overdue / mine_open. Archived projects are hidden unless include_archived=True.
|
| get_projectA | Full detail for one project (id or title): members, admins, boards with per-board open/done/overdue counts, settings, labels. |
| get_projects_summaryB | Per-project task statistics only (fast status overview): total, done, open, overdue, due today, my open/overdue, last completion. |
| list_labelsA | Labels of a kind: "task" (default) or "project". Task tools accept
these titles or ids in their |
| list_tasksA | List tasks with filters. The main task query tool. Where to look (pick one):
Filters (combine freely, applied exactly): board (title/id, needs project), assignee (name/id/"me"), unassigned, owner (creator), label (title/id), status "open"|"done"|"all", overdue_only, query (words that must all appear in title/notes/ checklist; Persian/Arabic letter variants match). sort: "deadline" (default; overdue first), "board" (kanban order, default for a project), "modified", "created". Paginated: returns total, has_more and next_offset. |
| list_my_tasksA | My tasks (assigned to me or personal), overdue first. Shortcut for list_tasks(scope="mine"). |
| search_tasksA | Find tasks by text, the way Mizito's own search page does (server side, includes archived projects), merged with an exact local match on title/notes/checklist of visible projects. status "open" | "done" | "all". Optional project narrows the result. Returns ids for get_task. |
| get_taskA | Everything about one task: full notes, assignees, deadline, checklist items (with ids), attachments, labels, completion, and its comments (+ change history if include_history=True). |
| get_task_commentsB | Comments on a task, newest first, with author names and mentions. |
| get_task_historyA | Change log of a task: who changed what (title, notes, assignees, board, deadline, completion...) and when, oldest first. |
| get_task_seenB | Who has opened a task, and when (first and last view per person). |
| get_user_workloadA | What one person (name/id/"me") has on their plate across all open projects: open task count, overdue, per project and per board, plus the task list (overdue first). Done tasks only if include_done. |
| daily_briefA | One-call standup: my overdue / due-today / no-deadline task counts with the urgent tasks listed, unread chats, and per-project open and overdue counts. Good first call for "what's going on?". |
| list_chatsB | Chats (DMs, groups, project group chats), most recent first: id, title (DMs are titled with the other person's name), kind, unread count, last message time. Filter by kind "dm"|"group"|"project" or by a title substring. Chat arguments elsewhere accept ids or titles. |
| read_chatA | Messages of one chat (id or title), newest first by default. Page back through history with offset (skip that many newest
messages): offset=0 then offset=30, ... |
| get_project_chatB | The group chat of a project (id or title). Same output as read_chat. |
| search_chatA | Search inside one chat (id or title), server side, newest first. query: text to find (Mizito's own in-chat search). from_user: only messages from this person (name/id/"me"). Give query, from_user, or both (both = server filters by text, then sender is checked locally). Paged with offset/next_offset. |
| search_messagesA | Search all chats at once (Mizito's global message search). Returns up to 15 hits per page with the chat each came from; page with offset/next_offset. |
| create_taskA | Create a task in a project. Assignees get notified: confirm with the user first unless they asked for exactly this task. project: id or title (required: Mizito has no project-less tasks). board: kanban column title/id (default: the project's first column). assignees: names/ids/"me"; default ["me"]; [] = nobody. reminder: when the task is scheduled ("زمان یادآوری"): this is the date Mizito uses for today / overdue. "2026-11-20 14:30" | "1405/08/30 14:30". deadline: "مهلت انجام", only in projects with the deadline feature. checklist: item titles. comment: first comment text. post_card_to_project_chat: put a task card into the project chat. Default: yes when the project has a chat, like the web app. Later changes to the task show up in the chat only if it has this card. |
| update_taskA | Edit a task. Only the arguments you pass change; everything else is sent back exactly as it is (Mizito's save replaces the whole task). assignees / labels replace the whole list; add_* / remove_* edit it. People and labels accept names or ids. remove_checklist takes item ids or exact titles (see get_task). add_checklist skips titles that already exist. To move columns use move_task; to complete use complete_task. Mizito has no partial update or version check: a change someone makes in the web app between this tool's read and its save is overwritten. |
| add_task_commentA | Post a comment on a task (the task's people are notified). reply_to = a comment id from get_task; mention = names/ids to @. |
| complete_taskB | Mark a task done (notifies the task's people, like the web app). |
| reopen_taskB | Mark a done task as not done again. |
| set_task_progressA | Set a task's progress percentage (0-99). For 100 use complete_task: in the web app 100% means done, and it asks before completing. |
| set_task_deadlineA | Set or clear (deadline=None) a task's deadline. Accepts "2026-11-20 14:30" (Gregorian, Tehran time), "1405/08/30 14:30" (Jalali) or ISO with Z. A date without time means 23:59 Tehran. |
| set_task_reminderA | Schedule a task ("زمان یادآوری"), or clear it with when=None. This is the date Mizito uses to put a task under today / overdue / upcoming, and when it reminds the assignees. Same date formats as create_task. (The web app calls this "snooze".) |
| move_taskA | Move a task to another kanban board (column) of its project. board: board title or id (within the task's project). position: "top" or "bottom" of the target column. |
| set_checklist_itemA | Tick or untick one checklist item. Same rules as the web app: no changes on a done or deleted task; an item someone else ticked can be unticked only by a project admin. When the last item gets ticked the result says all_items_done: the web app then asks whether to mark the task done, so ask the user and call complete_task (this tool never completes the task itself). |
| edit_task_commentA | Replace the text of one of my task comments (ids from get_task). |
| delete_task_commentC | Delete one of my task comments. |
| delete_taskA | Delete a task (Mizito keeps it restorable: see restore_task). Confirm with the user first. |
| restore_taskA | Undo delete_task for a task id deleted earlier. |
| bookmark_taskA | Star/unstar a task in my own task list (private to me). |
| send_messageA | Send a chat message. Teammates see it immediately: confirm wording with the user first unless they dictated it. to: chat title (project group / group) or a person's name (their DM is opened if it does not exist yet). Or pass dialog_id. reply_to: message id to reply to (from read_chat). mention: people to @mention (names or ids). Newlines are kept. Verified by reading the chat back. |
| edit_messageA | Change the text of one of my own messages. Mizito only allows this before anyone has seen it (the web app hides Edit after that). |
| delete_messageA | Delete one of my messages for everyone. Confirm with the user first. |
| mark_chat_readA | Mark every message in a chat as read (clears its unread badge). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 44 tools
Most tools target a distinct resource+action, but there are several self-acknowledged near-duplicates: get_dashboard_summary is explicitly 'the same data' as list_workspaces, get_project_chat returns 'same output as read_chat', get_task_comments duplicates the comments already in get_task, and list_my_tasks is a shortcut for list_tasks(scope="mine"). The descriptions do actively steer the agent ("prefer X", "shortcut for Y"), which keeps this usable, but an agent still has multiple plausible entry points for the same question.
Names are consistently snake_case verb_noun (get_task, list_tasks, set_task_deadline, delete_task_comment, search_messages), and the task/chat/project prefixes make families readable. A few exceptions break the pattern (whoami, daily_brief, health_check, bookmark_task) but they are memorable and unambiguous.
44 tools is well past the heavy threshold for a project/chat workspace server, and the surface includes redundant entries (dashboard summary, project summary, list_my_tasks shortcut, get_project_chat) that could be folded into existing tools. Many fine-grained setters (set_task_progress, set_task_deadline, set_task_reminder, set_checklist_item) add granularity that could plausibly be consolidated under update_task.
Task lifecycle is very thorough (create/update/delete/restore/complete/reopen/progress/deadline/reminder/move/checklist/comments/bookmark) and chat has send/edit/delete/read/search coverage. However there is no project or board creation/administration, no label management, and attachments are surfaced in get_task but cannot be uploaded or fetched — notable gaps for a workspace-management server.