Connect Claude Code, Codex, Cursor and other agents to your notes and tasks.
Morion runs a local MCP server next to your agents. Claude Code, Codex, Gemini Antigravity, Cursor, Cline, Zed and any MCP client get the same tools and the same data. A Claude session and a Codex session can work on the same board at the same time, on your machine, with every write attributed.
Settings · MCP Server
| Actor | Calls | Last seen |
|---|---|---|
| mcp:claude-code | 1,204 | 2m ago |
| mcp:codex | 318 | 41m ago |
| mcp:cursor | 57 | Yesterday |
The master switch, the five tool categories and the clients that called tools recently.
How it works
In detail
What it is not
What is MCP
Model Context Protocol is an open standard that lets an AI assistant call tools on a server. Instead of pasting context into every chat, your assistant connects to Morion and pulls what it needs on its own, and writes back.
The raw tools give any client the notebook and the board: search, read, create, claim, move, comment. The mo_* tools give it the engine: a work packet with the ticket and its context, an answer with a citation and a status on every claim, a conversational lookup.
Every write is logged with the actor: mcp:claude-code, mcp:codex, morion-concierge for Mo, user for you.
Every tool, by what it touches. 58 tools · v1.6.10
Every tool is available to every connected client, subject to the folder and note permissions you set. In the app the tools sit in five categories you can switch off one by one: Read (20), Create (9), Update (12), Delete (5) and Workflows (12). Below they are grouped by what they touch.
On the Free plan, external MCP clients get 1,000 calls a month; Pro has no limit. Calls from Mo and Auto-code, and failed calls, never count.
| mo_take_task | Primary pickup: ticket body, relevant comments, project brief, related lessons, specs, rules and topics in one call; optionally claims the ticket |
| mo_ask | Question answering over retrieved evidence: every claim cited and status-tagged, conflicts and gaps reported; scope by project, folder or kanban statuses |
| mo_find | Conversational lookup ("find that ticket", "similar to this note") with a per-hit reason |
| mo_search | Search across notes with Mo’s summary and keywords per hit; no synthesis |
| mo_list_projects | Project directory and topic vocabulary |
| mo_list_tasks_meta | Deterministic task metadata listing |
| mo_resolve_task | Resolve a task reference to its record |
| mo_remember | Store a workspace-wide fact; conflicts are surfaced, not overwritten |
| mo_forget | Remove workspace memory by pattern or entirely |
| mo_request_human | Durable escalation: a comment on the task or a backlog card |
| mo_check_workflow | Pre-flight gate for an intended action: allow, deny or ask the user |
| mo_build_workflow | Author an Auto-code workflow definition from a description |
| mo_regenerate_topic_doc | Rebuild one topic document |
Mo tools work only in folders where AI access is on, and never in a folder hidden from AI. What Mo writes is advisory: it never corrects your own edits.
| notes_search | Hybrid keyword + semantic search across all notes |
| notes_list | List notes with folder, tag and pinned filters, pagination, optional Mo metadata |
| notes_get | Fetch a note by ID with full body and tags |
| notes_create | Create a note with optional folder, tags and status |
| notes_update | Partial update; only provided fields change |
| notes_append | Append text to a note without rewriting it |
| notes_delete | Soft-delete to trash |
| notes_duplicate | Clone a note with a fresh ID |
| notes_move | Move a note to another folder |
| notes_recent | Last N notes by update time |
| notes_list_activity | Unified comments + audit feed, cursor-paginated |
| notes_add_comment | Post a comment, optionally as a reply |
| notes_update_comment | Edit your own comment |
| notes_delete_comment | Remove your own comment, audit-logged |
| notes_list_attachments | Attachment metadata only, cheap to call |
| notes_get_attachment | Returns an attached image so the agent can see it |
| tasks_list | Tasks in a kanban folder, filtered by status and date |
| tasks_claim | Atomically claim a todo or reopened task into doing; no races between agents |
| tasks_move | Move a card between columns with a message, or reorder within a column |
| tasks_history | Full status-transition history: who moved what, when |
Seven columns: note · backlog · todo · doing · review · reopened · done. A task is a note with a status: same search, same folders, same permissions.
| workflows_list | List Auto-code workflows for a project |
| workflows_create | Create a workflow definition |
| workflows_update | Update a definition |
| workflows_copy | Copy a workflow |
| workflows_delete | Delete a workflow |
| workflows_validate | Validate a definition before installing it |
| workflows_environment | Report the agents and settings available to workflows |
| projects_set_auto_code | Turn Auto-code on or off for a project and pick its default workflow |
| auto_code_workspace_settings | Read or change the workspace-wide Auto-code settings |
The morion-workflows skill teaches an agent to author and install these safely.
| folders_list | All folders, ordered |
| folders_create | Create a folder |
| folders_rename | Rename |
| folders_delete | Delete |
| folders_duplicate | Clone with notes |
| folders_move | Move in the sidebar |
| folders_reorder | Reorder by ID list |
| folders_set_project | Move a folder to another project (re-indexes) |
| folders_set_view_mode | List or kanban view |
| folders_get_auto_code | Read a folder's Auto-code settings |
| folders_set_auto_code | Turn Auto-code on or off for a folder and choose its workflow |
| tags_list | List tags |
| tags_create | Create a tag |
| tags_update | Rename or recolor |
| tags_delete | Delete; notes keep their content |
| audit_recent | Last N audit entries: what each client changed |
Every MCP write is logged with the client name.