MCP

Tools and privacy

Once connected, these are the tools it can call. Reading is free to use; writing is deliberately narrow, so you always know how something got into your map.

Reading tools (16)

vinc_whoamiWhich graph you are connected to, and which spaces you can reach: personal or a team, with your role in each.
vinc_conventionsRead your conventions before writing: node kinds, relations, your topics, your ratified vocabulary.
vinc_searchFind concepts and documents by meaning or keyword.
vinc_briefOne question in, the material for an answer out: the node, its canonical excerpts, and its relations. Nothing is generated.
vinc_graphWalk out from one concept to see what it connects to.
vinc_recallList recent episodes, narrowed by topic or tag.
vinc_decideGather what bears on a decision, including conflicts.
vinc_domainsList the topics your material actually formed.
vinc_suggest_tiesPropose link candidates for a node by tag and domain proximity.
vinc_neighborsLook at a single hop around one node.
vinc_pathTrace the shortest chain between two concepts.
vinc_merge_candidatesPropose concepts that look like duplicates of each other.
vinc_merge_rejectionsList the pairs you already ruled out as duplicates, and why.
vinc_diagnoseSpot orphans and clusters in the structure.
vinc_doc_getReconstruct a document's canonical text, verified by hash.
vinc_doc_listList your documents with title, origin, and chunk count.

Writing tools (8)

Eight, and four of them destroy something. They are kept narrow so an assistant cannot rearrange your map into something whose origins you can no longer trace.

vinc_ingestWrite new concepts and links into the map.
vinc_doc_putStore or edit a document's canonical text.
vinc_doc_extractDerive concepts from a stored document. Proposes first; writes only when you approve.
vinc_merge_rejectRecord that two concepts are not duplicates. Reversible.
vinc_deleteIrreversibly delete one node and every edge attached to it.
vinc_delete_edgeDelete one relationship. Both nodes stay.
vinc_merge_nodesIrreversibly fold two concepts that turned out to be one.
vinc_doc_deleteDelete a document, its chunks and identity together.
The last four cannot be undone. Each is marked destructive in the protocol, so a host that honors those hints will ask you before running it. Do not rely on that alone: keep a backup before letting an assistant reorganize anything at scale.

What is deliberately not exposed

Theme and vocabulary management is HTTP-only and never reaches MCP. An assistant can propose a new type, which lands as proposed for you to ratify, but it cannot ratify its own proposal. The judgment about what your vocabulary is stays with you.

The structuring happens in the assistant, not in Vinc. Vinc holds no model and no API key, which is why it runs offline. The assistant reads your material, decides what the concepts and relationships are, and writes them in. Vinc stores exactly what it is given and never guesses at meaning. Different assistants will phrase that structure differently, and that is the point: the judgment stays yours to choose.

What leaves your machine

Locally: nothing. Over stdio the assistant runs Vinc as a tool on your own computer. Your files are never uploaded. The assistant sees only the answers to the specific tools it calls, never the documents behind them.
Through a connector: only what you chose to sync. The hosted graph holds the topics you explicitly selected, isolated to your account. See the privacy policy for the full account picture.

Limits

The free plan gets 2,000 connector tool calls a day, the same as Pro. What it caps is topics: 5 of them. Reaching that limit blocks new topics only, so everything you already have keeps working, and Pro removes the cap. Local stdio connections have no limits at all: they run on your own computer, so there is nothing to meter.

Account isolation

On the hosted graph, every read and write is forced to the signed-in account. If an assistant names a different owner, that value is discarded and replaced with the session's owner.