Using Nisa with Merv

Nisa and Merv share a RapidReview sign-in and a product switcher; they don’t call each other. The bridge is an arXiv id your agent carries across. Concept: How Merv and Nisa fit together.

Find the paper in Nisa

nisa search "direct preference optimization" --max-results 5
nisa related 2305.18290 --n 10

Cite it in Merv

Your Merv-connected agent calls litreview.cite (an MCP tool call, not a shell command):

{
  "project_id": "proj_…",
  "arxiv_id": "2305.18290",
  "targets": [{ "type": "experiment", "id": "exp_…" }],
  "note": "baseline for the alignment comparison"
}

Exactly one of url / doi / arxiv_id (else provide exactly one of url, doi, or arxiv_id); up to 20 targets of type litreview_section, experiment, or claim; note ≤ 300, title ≤ 200 characters.

Keep the review current

A targeted litreview.edit afterwards. In plans, cite portably — arXiv:2305.18290 — never Merv’s internal paper_… id.

Merv deduplicates arXiv/DOI/URL forms of one paper and fetches metadata from arxiv.org, ar5iv.org, openreview.net, semanticscholar.org, aclanthology.org, nature.com, paperswithcode.com, doi.org, dx.doi.org; other hosts register with the title you pass. Nothing flows automatically and nothing records that a citation came from Nisa. Your agent can run nisa itself if the Nisa skill is installed next to the Merv plugin — Install → Give your coding agent the skill.

⌘I

Start

Guides

Reference