review_status, get_feedback, send_artifact, add_files) instead of CLI commands. The behavior is identical — the MCP server connects to the same Unix socket internally.
When registered in skills mode, agents invoke the corresponding CLI commands below.
When the agent’s working directory differs from monocle’s, use
--workdir (-C) to point commands at the correct repository. Alternatively, set MONOCLE_SOCKET or MONOCLE_WORKDIR to achieve the same effect via environment variables. Without one of these, commands look for a socket based on the current directory and may not find a running session. Press I in the monocle TUI to see the active socket path.monocle review status
Check the current review status of the running monocle session.
Flags
Output
Without--json, prints a status string or summary. The status reflects whether feedback is pending, a pause has been requested, or the session is idle.
MCP tool equivalent
In MCP tools mode, call thereview_status tool with no parameters.
monocle review get-feedback
Retrieve pending review feedback from the queue.
--wait, the command returns immediately. If no feedback is pending it prints No feedback pending. and exits.
Flags
MCP tool equivalent
In MCP tools mode, call theget_feedback tool:
monocle review send-artifact
Send content to the reviewer — a plan, architecture document, summary, or any other text — so it appears in the monocle sidebar alongside file diffs.
--id, monocle updates the existing entry and shows a diff between the old and new versions.
When --file is not provided, the command reads content from stdin.
Flags
Reading from stdin
Reading from a file
MCP tool equivalent
When using MCP tools mode, thesend_artifact tool accepts these parameters:
monocle review add-files
Add one or more files or directories to the current review session so they appear in the monocle diff viewer.
Arguments
Flags
MCP tool equivalent
In MCP tools mode, call theadd_files tool: