Documentation

MCP tools

Ryvem registers 60 MCP tools across 14 families (plus 3 deprecated kb_* aliases). Every tool works in any MCP client. You will rarely call them by hand — the workflow flows and the agent harness orchestrate them for you — but each is a first-class tool you can invoke directly.

How tools relate to flows

The ten workflow flows and the harness call these tools in the right order, so most days you drive Ryvem through a flow, not a tool. Where a client lacks prompt or slash-command support, the guide tool returns the same flows step by step. The handiest tools to run directly are board (your tasks by column), task (detail plus the live delta), search_tasks, prs/pr_diff (review the team's PRs) and memory_search (recall anything from the graph).

Naming and count

Names below are the exact registered tool names. The three knowledge-base tools also register byte-identical kb_search / kb_page / kb_spaces aliases, kept for one release — they are not counted in the 60.

Board 13 tools

Read and drive the cards on your board — Jira, Trello or the zero-config local board — through one provider-agnostic surface.

ToolWhat it does
boardsLists the active provider's boards (those with your open tasks by default; all shows every visible board). Never picks one for you.
use_boardSelects the session's active board and returns its columns in flow order.
boardYour open tasks on the active board, grouped by column and annotated with local work memory (branch/PR/merged).
taskFull detail of a task plus its live delta: description with acceptance criteria, links, subtasks, new images inlined and only the comments new since your last check.
moveMoves a card by applying the matching transition; to accepts a column name, a status name, or "next".
commentAdds a markdown comment to the card, written in the board's language with no AI references.
assignSets a task's assignee — a provider account id, or the literal "me".
link_tasksCreates a directional issue link between two tasks (blocks, is blocked by, duplicates, relates to, …).
search_tasksSearches tasks across the provider (native query language such as JQL, or free text), with mine, assignee and limit filters.
membersLists the users assignable to the active board's project (name, email, accountId).
create_taskCreates a card in the active project from an issue type and summary; parentKey makes it a subtask.
subtasksThe subtask picture around a card: children and a done/total figure on a parent, or parent and siblings on a subtask.
checklistReads and toggles the acceptance-criteria checklist (- [ ] / - [x]) in the card description.

Work 6 tools

The task lifecycle backed by the memory graph: branch memory, refinement, closing and the board plan.

ToolWhat it does
startStarts or resumes a task: decides between continuing the existing branch or creating a new one — using branch memory, git and PR state — and persists the decision.
refineReplaces the card description with your refined markdown (restructured and lossless), recorded in local memory when a repo is bound.
finishCloses a task's work cycle: with prUrl records the PR on the current branch, without it marks the task done, and logs the event.
historyThe repo's work memory — work items with their branches (base, PR, merged) and latest events — after a merge-aware refresh.
planPersists and reads the board execution plan (order, dependencies, overlaps, notes) in the memory graph.
suggestRecords an improvement suggestion as a searchable memory node — surfaced via memory_search, never applied to your files.

Project 5 tools

Repo intelligence, skill packs and opening/tracking pull requests.

ToolWhat it does
projectDetects the repo stack, lists the local conventions found (which take precedence over skill packs) and the applicable packs, and sets the active repo.
skillThe built-in engineering skill packs: a table of all packs, or one pack's full markdown content.
prOpens a pull request for the current branch (GitHub or Bitbucket, detected from origin); title and body in English, with no AI references. base can target another task's branch for a stacked PR.
pr_statusRich status of a PR by number: state, merge target, mergeability, approvals and the aggregated CI/checks state.
pr_commentPosts a comment on a PR, in the PR's language, with no AI references.

Docs / knowledge base 3 tools

Query a Confluence knowledge base. The flows consult it automatically while refining and working a task; you can also query it by hand.

ToolWhat it does
docs_searchSearches the knowledge base (CQL when the query looks like it, free text otherwise), optionally scoped to one space.
docs_pageReads a full page as markdown, with metadata and URL — by id (preferred) or title.
docs_spacesLists the spaces you can see (key, name, type) to discover a space to scope a search.

Each also registers a deprecated, byte-identical alias: kb_search, kb_page, kb_spaces.

Attachments 1 tool

ToolWhat it does
attachmentReads one card attachment by id — PDF, XLSX, CSV, text and code extracted to text, images inline — cached content-addressed so re-reads cost no download.

Conversation 3 tools

Talk to the team on the card without blocking: ask, track and conclude clarification threads.

ToolWhat it does
askPosts a question to the team as a card comment with real @mentions and records it as an open thread in local memory.
resolve_threadConcludes an open ask thread: posts a visible completion comment starting with "✅" and marks the thread resolved.
threadsValidates pending clarifications: scans tracked threads and checks each card live for a reply, listing what still waits.

Review 6 tools

Code review of the team's PRs on both sides of the conversation. The same PR scope that opens PRs is enough to list, comment inline, reply, resolve and approve — it can never reject.

ToolWhat it does
prsLists open PRs to review (others' by default; mine/all change the scope), each with a reviewed-since marker.
pr_diffThe full review context: header, changed files, the unified diff per file, comment threads (with NEW-since-last-pass flags) and your previous review.
pr_reviewSubmits a review — inline comments with event "comment" (default) or "approve"; request-changes is impossible by construction.
pr_replyReplies to a specific existing review comment, threaded under its commentId (optionally resolving the thread).
pr_resolveResolves (or, with reopen, reopens) a review thread by its threadRef.
pr_request_review(Re-)requests reviewers and/or marks a draft PR ready for review.

Memory 4 tools

Read the temporal memory graph, where nothing is ever deleted, plus the budgeted repo map. See the Memory graph reference.

ToolWhat it does
memory_searchFull-text search of the graph (tasks, PRs, reviews, conversations, plans, suggestions) with optional kind/scope filters; returns compact hits.
memory_getExpands one node by id — any version, including superseded ones — with its full body and structured data.
memory_historyThe full supersedes chain of a node (oldest first), so you can see how a task, review or plan evolved.
repo_mapA ranked, token-budgeted symbol skeleton of a repo (files with their key definitions), cached per git blob hash.

Graph 1 tool

ToolWhat it does
graph_exportRenders the entire temporal memory graph to one self-contained, offline HTML file — a force-directed map with search, filters and supersede-chain history — and returns the file path plus node/edge counts.

Harness 5 tools

Drive the deterministic agent harness. The universal entry point is harness_next; the full model is in the Agent harness reference.

ToolWhat it does
harness_nextThe self-driving entry point: acquires the loop lease and returns the pending or next brief to execute as a role, or reports the loop done.
harness_reportSubmits the pending brief's report; the engine validates it, runs the step's gates, and advances the loop or embeds feedback in a bounded retry.
harness_statusLists the live agent loops and their state (kind, status, step, iteration, pending brief) without advancing anything.
harness_configWrites the agents block of ryvem.json — enabled roles, execution mode, loop budget, model tiers, per-role tiers.
harness_abortTerminally aborts a loop and releases its lease; it serves no further briefs.

Onboard 2 tools

Deep-read a repo into memory, incrementally — a full read once, then git-anchored deltas.

ToolWhat it does
onboard_statusResolves the repo and its anchor: no anchor returns the full deep-reading protocol; an anchor returns the exact targeted delta work list (re-read / new / verify-removed / renames).
onboard_recordPersists the codebase map, business rules (with evidence), glossary, objective and any removals into the graph, and writes the new git anchor.

Guide 1 tool

ToolWhat it does
guideReturns the complete step-by-step instructions of a workflow (start-session, work, run-board, review-pr, define-task, …). Call without arguments to list the flows. Works in every MCP client, including those without prompt support.

Setup 2 tools

The provider-agnostic entry points for bootstrapping a new project.

ToolWhat it does
workspacesLists the workspaces (Trello organizations, Jira projects) the resolved account can create boards or cards inside.
create_boardCreates a new board in a workspace when the provider supports it (e.g. Trello); providers that cannot (e.g. Jira) return an actionable error.

Config 8 tools

List, inspect and edit the global profile store in a conversation with the user. Destructive tools require an explicit confirm: true; secrets are always redacted. See Configuration.

ToolWhat it does
config_listLists every configured profile (provider, default flag, which accounts are present). Read-only and secret-safe.
config_showShows one profile's fields; token fields are redacted, never returned in full.
config_setSets a dotted field on a profile (e.g. board.url); overwriting an existing value needs confirm: true.
config_unsetRemoves a dotted field from a profile. Destructive: needs confirm: true.
config_add_profileCreates a new profile seeded with its board provider (jira, trello, or local).
config_remove_profileDeletes a profile and all its credentials, reassigning the default if needed. Destructive: needs confirm: true.
config_set_defaultPoints the default profile at an existing profile. No data is lost.
config_clearWipes every profile from the global config. The most destructive config tool: needs confirm: true.