datacore-mcp
OfficialRelated Servers
Alternatives to datacore-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceThis MCP server lets any compatible AI assistant read, extend and connect the matters in a person's life — plans, trips, people and places — from a repository that belongs to the user, so a new assistant picks up where another left off. It keeps the user's words verbatim, records every change, and stores the repository as a plain file on the user's own computer.14126 npmApache 2.0
- MIT
- AlicenseBqualityAmaintenanceMCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.8932 PyPI6Apache 2.0
- AlicenseNot gradedqualityFmaintenancePersonal AI cognitive exobrain server providing long-term, emotionally-tagged memory and task management for LLMs via MCP.1MIT
- AlicenseNot gradedqualityAmaintenanceOpen-source MCP memory server providing persistent, cross-platform context for AI tools via a knowledge graph with encrypted storage.29 npm13AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceMCP server providing persistent AI memory with four-tier retrieval (SQLite FTS5, graph, vector, LLM agent) to give AI assistants structured, long-term memory without RAG.1Apache 2.0
TDQS
Scored across 5 tools
datacore_capture and datacore_ingest both create knowledge notes, so an agent may struggle to choose between recording a note and ingesting text content; the other three tools are clearly distinct. Descriptions offer some guidance (capture for proactive journaling, ingest for text content), but the boundary remains fuzzy.
All tools use the same datacore_ prefix and lower snake_case with a single descriptive word, making the set highly predictable. No mixed conventions or inconsistent verb styles are present.
Five tools is well-scoped for a personal knowledge/note management server, covering status, capture, date utility, ingest, and search. No tool feels redundant enough to remove, though capture/ingest overlap is a content issue rather than a count issue.
The surface covers creation (capture/ingest), retrieval (search), status, and date utilities, but lacks update/delete operations and direct note retrieval by identifier. For a knowledge base, the inability to edit or remove notes is a notable lifecycle gap.