MCP tool reference
This page lists every tool a connected AI client can call through Orbit’s remote MCP connector — 22 tools plus 12 guided workflow prompts.
Every call runs as the signed-in user: read tools see only what you can see, and write tools require your write access plus an editor seat.
Find and read notes
Section titled “Find and read notes”| Tool | What it does |
|---|---|
orbit_list_workspaces | List the Orbit workspaces accessible to the signed-in user. |
orbit_list_notes | List folders and markdown notes in one workspace. |
orbit_search_notes | Search indexed notes across all accessible workspaces or one workspace. |
orbit_resolve_note | Resolve a note hint, path, or URL into an exact note reference. |
orbit_get_note | Read a note as raw content, full metadata, a document map for safe edits (sections, tables, and meeting blocks), a single section, or agent-ready context. |
orbit_get_folder | Read a folder page: its notes, connections to other folders and notes, and incoming references. |
orbit_list_comment_threads | Read a note’s comment threads in full — authors, messages, replies, reactions, resolved state, and where each thread is anchored. |
orbit_get_workspace_graph | Return the workspace’s wiki-link graph. |
Comments are visible to AI clients
Section titled “Comments are visible to AI clients”The full, document-map, and section formats of orbit_get_note report where your comment threads are anchored — a note-level summary, plus a per-section and per-table list for the document map. Only the commented text is shared; the comment messages themselves never leave Orbit.
This lets a client preserve commented passages when it edits. When an edit does destroy the anchored text, the write result reports it as commentImpact, and a well-behaved client tells you which comments lost their anchor. Those comments are not deleted — they show as unanchored in Orbit, and reattach if the text comes back.
Create and edit notes
Section titled “Create and edit notes”| Tool | What it does |
|---|---|
orbit_create_note | Create a new markdown note by path; refuses to overwrite existing notes. |
orbit_append_to_note | Append to the end of a note or to a chosen heading section; never replaces existing content. |
orbit_patch_note | Make surgical edits: exact text replacement, block replacement, section replacement, or insert after a heading. |
orbit_upload_asset | Upload a binary attachment to a note and return ready-to-insert markdown. |
orbit_add_meeting_block | Add a native meeting notes block to a note from your client’s summary and the transcript as plain copied text (no file needed); a summary alone is enough. |
There is deliberately no full-note overwrite tool: edits stay localized so open collaborative editors stay in sync.
Edit tables
Section titled “Edit tables”These tools edit existing markdown tables atomically, protected against stale reads by table hashes.
| Tool | What it does |
|---|---|
orbit_insert_table_rows | Insert rows into a table. |
orbit_update_table_cells | Update individual body cells. |
orbit_delete_table_rows | Delete body rows. |
orbit_move_table_rows | Move rows from one table to another atomically. |
Organize and delete
Section titled “Organize and delete”| Tool | What it does |
|---|---|
orbit_move_note | Move or rename one note within a workspace; never deletes content. |
orbit_delete_note | Move one note to Recently Deleted — a restorable soft delete, not a permanent delete. |
orbit_delete_folder | Recursively delete a folder; child notes go to Recently Deleted, and folders containing non-note files are rejected by default. |
Deleted notes are restorable in Orbit — see Versions, export, and trash.
Diagnose problems
Section titled “Diagnose problems”| Tool | What it does |
|---|---|
orbit_doctor | Return connector version, instructions, and advertised capabilities. |
orbit_get_write_status | Check whether a timed-out write was received, applied, persisted, or failed. |
Run guided workflows (prompts)
Section titled “Run guided workflows (prompts)”Clients that support MCP prompts also get 12 guided workflows. Prompts are instructions, not tools — they do not modify Orbit by themselves.
| Prompt | What it does |
|---|---|
orbit_query_wiki | Answer a question from wiki content, with citations and no writes by default. |
orbit_summarize_workspace | Summarize a workspace using search, graph, and note context. |
orbit_note_briefing | Brief you on one note plus its backlinks, links, and related notes. |
orbit_lint_wiki | Inspect a workspace for wiki health issues and propose reviewable fixes. |
orbit_find_contradictions | Identify conflicting statements or stale assumptions. |
orbit_build_context_pack | Build a bounded, cited context pack for an external task. |
orbit_draft_from_related_notes | Draft new markdown from related notes and link context. |
orbit_append_meeting_notes | Turn raw meeting notes or a transcript into a summary and add it to a note as Orbit’s meeting block. |
orbit_ingest_source | Turn one source note into cited wiki updates or candidate pages. |
orbit_promote_candidate | Review a candidate note and promote it into the wiki after confirmation. |
orbit_prepare_ai_ready_wiki | Prepare a normal workspace for AI-assisted wiki workflows. |
orbit_collect_context | Collect all Orbit context connected to a client or topic folder, following folder connections across accessible workspaces. |
Up next: teach your client Orbit’s conventions with the Agent Skills.