Tacitus MCP Server

Long-term memory for AI agents: local-first PKM with provenance and hybrid search.

Local serverstdioPython

What is the Tacitus MCP server?

Long-term memory for AI agents: local-first PKM with provenance and hybrid search. The tacitus mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

Tacitus is an MCP server that turns any folder of Markdown notes into an agent-native knowledge base. It gives AI agents (Claude Code, Claude Desktop, and any MCP client) three things they actually need:

Its toolset

Everything the assistant can do here goes through one of these:

  • Group — Tools
  • Memory — remember, recall, forget
  • Retrieval — search, get_note, graph_query, list_notes, properties_query*
  • Write-back — propose_changes, commit_changes, revert, rename_note*, delete_note*, get_version*
  • Convenience — create_note, update_note, link, tag, audit_log
  • Templates — list_templates*, create_from_template*
  • Tasks — list_tasks*, toggle_task*
  • Meta — capabilities

Adding it to your client

The server ships on npm as @dashiro/tacitus-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tacitus's toolset — Group, Memory, Retrieval and 5 more — is a fair guide to whether it matches your workflow. It is maintained by ionasrobert; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Tacitus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tacitus mcp server does with a few real requests.

Available tools

ToolWhat it does
GroupTools
Memoryremember, recall, forget
Retrievalsearch, get_note, graph_query, list_notes, properties_query*
Write-backpropose_changes, commit_changes, revert, rename_note*, delete_note*, get_version*
Conveniencecreate_note, update_note, link, tag, audit_log
Templateslist_templates*, create_from_template*
Taskslist_tasks*, toggle_task*
Metacapabilities

How to install the Tacitus MCP server

{
  "mcpServers": {
    "tacitus": {
      "command": "npx",
      "args": ["-y", "@dashiro/tacitus-mcp-server", "/path/to/your/vault"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Tacitus to Group.
  • Use Tacitus to Memory.
  • Use Tacitus to Retrieval.

Frequently asked questions

It connects Tacitus to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Group, Memory, Retrieval, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Tacitus directly.