Maito MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAITO_URL | Yes | URL of your Maito workspace (e.g., https://maito.romankov.dev) | |
| MAITO_TOKEN | Yes | Authentication token obtained from Maito (Sidebar → Connect AI) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Identify the user and their environment. Returns email, local timezone of this MCP process, the Maito instance URL, and number of workspaces. Call first when you need user context. |
| list_workspacesA | List all workspaces. Each workspace is an isolated container — spaces/boards/cards/notes do not cross workspace boundaries. Call this first to orient yourself. |
| list_spacesA | List spaces. If workspaceId is omitted and there is exactly one workspace, uses it; otherwise returns spaces from all workspaces labelled with workspaceId. |
| list_boardsA | List boards. Filter by workspaceId and/or spaceId. Each board includes workspaceId + spaceId. |
| list_columnsA | List columns (statuses) of a board, ordered left-to-right. Use before create_card / update_card to pick the right column by name. |
| list_tagsA | List tags. Tags are scoped to a space. Filter by spaceId or workspaceId. Use to resolve tagIds to human-readable names. |
| list_cardsB | List cards (summaries). Filter by workspaceId, boardId, done, archived, priorityOnly. Each card includes workspaceId + boardId + columnId. |
| get_cardA | Return a single card with full details: description, resolved tag names, journal entries, subtasks, plus board/column/workspace context. |
| search_cardsB | Full-text search across card titles and descriptions. Optionally scope to workspaceId / boardId. |
| create_cardA | Create a task card. Either columnId (precise) or boardId (uses first column). Workspace inherited from column/board. |
| update_cardA | Update card fields. patch.columnId MOVES the card to another column (mark Done by moving, or pass done:true). Omit fields you do not want to change. |
| archive_cardA | Archive a card (soft-delete — recoverable from Archive view). |
| add_journal_entryC | Add a comment / journal entry to a card. Use for status updates, notes, decisions. |
| create_spaceC | Create a new space (top-level container) within a workspace. |
| create_boardA | Create a new board inside a space. Spawns 3 default columns: Todo / In Progress / Done. |
| create_columnC | Create a new column (status) in a board. |
| search_notesC | Search notes by title and body. Optionally scope to workspace. |
| get_noteB | Get full body of a note by id. |
| create_noteC | Create a new note. workspaceId required when multiple workspaces exist. |
| today_planB | Return cards scheduled for today in the local timezone of this MCP process. Pass dayOffset=1 for tomorrow, -1 for yesterday. Filter by workspaceId. |
| recent_activityB | Activity feed: card_created, card_done, card_moved, board_created, space_created, note_created, etc. Answers "what did I do recently". |
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 21 tools
Each tool targets a distinct action and resource, with clear descriptions that prevent confusion. For example, add_journal_entry is specifically for journal entries on cards, while create_note is for standalone notes.
All tool names follow a consistent verb_noun pattern using lowercase with underscores, such as list_boards, create_card, and archive_card. This makes the API predictable and easy to navigate.
With 21 tools, the server covers the core operations for a project management system but is slightly above the typical 3-15 range. However, each tool serves a clear purpose and the count is not excessive.
The tool set covers create, read, list, search, and some update/archive operations, but notable gaps include missing update and delete tools for boards, columns, spaces, and notes. This leaves some lifecycle management incomplete.