Agents

OpenClaw

OpenClaw is one agent runtime that speaks MCP. There are two ways to give it the graph, and they are not exclusive: the standard registration every MCP host has, and a plugin that lets its own memory search reach Vinc.

Both ways read with a read-only key. Neither replaces OpenClaw's built-in memory, and neither extracts anything from a conversation. The general rules for an agent on Vinc, citations first, are on the Agents page.

1. Standard MCP registration

Add Vinc under mcp.servers in ~/.openclaw/openclaw.json and restart the gateway. Vinc's tools then appear beside OpenClaw's own, and the agent calls them when it decides to.

{
  "mcp": {
    "servers": {
      "vinc": {
        "url": "https://mcp.vincs.io/mcp",
        "transport": "streamable-http",
        "headers": { "Authorization": "Bearer vinc_ro_…" }
      }
    }
  }
}

The limit of this way in is the one every MCP host has: the agent has to decide to call a Vinc tool. Nothing is recalled unless it asks, and the tool definitions cost context tokens.

2. The plugin: memory search that reaches Vinc

The plugin adds one thing on top of the above. It makes OpenClaw's own memory_search and memory_get reach the Vinc graph, so the agent does not have to decide to call a Vinc tool.

It registers through registerMemoryCorpusSupplement, which is non-exclusive: it does not take the exclusive memory slot and does not replace memory-core. The bundled memory-wiki plugin uses the same path. The exclusive slot would have given system-level auto-recall and taken the slot from everything else, a worse trade for a memory meant to sit beside a person's own notes.

{
  "plugins": {
    "entries": {
      "vinc": {
        "enabled": true,
        "config": {
          "apiKey": "vinc_ro_…",
          "url": "https://mcp.vincs.io/mcp"
        }
      }
    }
  }
}

Search results come back with a path of the form vinc://doc/<doc_id> or vinc://node/<node_id>, and memory_get takes that path as it is: the document's full text, or the node's properties, relations and citations.

What this does not do

• No automatic extraction from conversations, on either path.
• The supplement does not write.
• It does not replace memory-core. It sits beside it.