mindwiki_capture

Quick-capture content into your vault inbox. The path is auto-generated under capture/ with the date and a slug derived from the title.

Scope: OAuth mcp:capture or mcp:write; personal API key write

Parameters

Parameter	Type	Required	Description
`content`	string	Yes	Content to capture
`title`	string	No	Optional title (defaults to Capture)
`idempotency_key`	string	No	Unique operation key, 1–128 characters. Reuse with unchanged title/content after a timeout.

Example Request

json

{
  "tool": "mindwiki_capture",
  "arguments": {
    "content": "Interesting idea about feedback loops in team dynamics — the same pattern shows up in complex systems.",
    "title": "Feedback loops in teams",
    "idempotency_key": "team-feedback-capture-001"
  }
}

Example Response

json

{
  "path": "capture/2026-05-09-14-22-00-feedback-loops-in-teams-a1b2c3.md",
  "content_hash": "9d4f2c8...",
  "seq": 415
}

The captured page is stored as standard markdown with frontmatter. From there it lives in your capture/ folder until you move it elsewhere or link it from somewhere else in the vault.

With an idempotency key, concurrent calls and lost-response retries return the original saved page instead of creating duplicates. Changing the payload under the same key returns an MCP tool error with code IDEMPOTENCY_CONFLICT. Without a key, each call creates a separate capture.

The REST counterpart is POST /vault/capture, whose separate contract does not currently accept the MCP idempotency key.