Neurnav MCP Server

other

This is the MCP endpoint behind Neurnav's document collaboration model, and it's what lets Neotask branch, review, and merge changes to reports the same way a developer would branch code. Every change carries provenance — whether a human or the AI made the edit — so when a revision gets merged, the history of who touched what stays intact. Ask Neotask to open a branch on a document, make a set of edits, and merge them once you've reviewed the diff.

• Branch a document before editing it, keeping the current version stable
• Track whether each change came from a human or an AI edit
• Merge a reviewed branch back into the document's main line

What you can automate

Neurnav MCP Server

Branch, review, and merge changes to reports and research documents with AI and human provenance tracking through Neurnav's document collaboration service.

Real workflows

Merge AI-drafted edits with a clear paper trail

You have Neotask draft a revision to a research document on its own branch. Because the server tags the edit as AI-authored, anyone reviewing the merge later can see exactly which paragraphs came from the model versus a person, then approve the merge with that context.

Frequently asked questions

How is this different from the main Neurnav connection?

This is the MCP server surface specifically — it's what Neotask talks to under the hood to branch, diff, and merge documents; the provenance tracking (human vs. AI) is a defining feature of this endpoint.

Can I tell which edits Neotask made versus a teammate?

Yes — every change carries a provenance tag, so a merged revision still shows who or what authored each part.