A local cognitive memory server for MCP-compatible AI agents, providing persistent, inspectable memory with spaced repetition, predictive retrieval, and a 3D dashboard, all running locally in a single Rust binary.
34
4 npm
648
AGPL 3.0
Why this server?
Facilitates multi-machine setups by synchronizing corpus and agent definitions via Syncthing, allowing dedicated ingestion servers.
Enables AI assistants to manage a personal markdown-based knowledge base with natural language interactions. Supports creating, searching, updating, and organizing notes across categories like people, recipes, meetings, and procedures.
11
1
-
Why this server?
Provides tools for interacting with one or more Syncthing instances through the Syncthing API. Read-only by default, it exposes monitoring and operational capabilities such as system/folder status overviews, device and folder listing, connection and event inspection, and disk events, with paginated and bounded responses. Optional write, destructive, and administrative gates enable mutations such as triggering scans, changing folder destinations within allowed path roots, and trust/sharing/security administration, with multi-instance selection and per-instance credentials.
Enables secure, configurable access to one or more Syncthing instances over MCP, with read-only defaults and opt-in write, destructive, and administrative operations. Supports stdio and authenticated Streamable HTTP transports, typed tools, bounded responses, and multi-instance configuration.
40
MIT
Why this server?
Provides tools for monitoring and controlling Syncthing via its REST API, including getting system status, listing and checking folders and devices, viewing connection status, and triggering folder scans.
Enables AI agents to maintain a shared, serverless, conflict-free knowledge graph across multiple machines by syncing append-only per-node shards. It provides drop-in compatibility with the official MCP memory tools while converging automatically without merge conflicts.
Mozilla Public 2.0
Why this server?
Integrates with Syncthing to monitor synced Claude Code project folders, attribute files to machines via the Syncthing REST API, detect offline sync devices and conflict files, and recover deleted sessions from Syncthing's versions folder.
Gives every Claude surface (claude.ai, Desktop, mobile, Office add-ins, Claude Code) read and write access to the memories, transcripts and notes produced by Claude Code instances on all of your machines, with hybrid keyword and semantic search. Runs as a self-hosted remote MCP server with GitHub allowlist authentication, secret redaction and audit logging.
MIT
Why this server?
Allows for the management and monitoring of Syncthing file synchronization instances, providing capabilities to configure folders and devices, monitor system status and connectivity, and perform administrative actions such as rescanning folders or pausing synchronization.
A comprehensive MCP server providing 35 tools for monitoring and managing multiple Syncthing file synchronization instances. It enables users to track sync status, manage device connections, and modify folder configurations through natural language commands.
2
MIT
Why this server?
Allows processing and updating listening metrics from Musicolet backup files that are synchronized via Syncthing, by monitoring a Syncthing drop folder for new backups.