Skip to main content
Glama
datacore-one

datacore-mcp

Official
by datacore-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to datacore-mcp

No user-submitted related servers found.

    Related Servers

    • coding-os

      kouroshez
      A
      license
      B
      quality
      A
      maintenance
      MCP 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.
      87
      6
      Apache 2.0

    • Hippocampus

      karrolcia
      A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP memory server providing persistent, cross-platform context for AI tools via a knowledge graph with encrypted storage.
      1 npm
      13
      AGPL 3.0

    • supermem

      lamenting-hawthorn
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      1
      Apache 2.0

    • Mnemo

      oyekamal
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing a persistent, temporal memory brain for AI assistants, enabling cross-session recall of facts with relationships and temporal context.
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: capture for journal entries, ingest for knowledge notes, search for querying, status for system health, and date for date operations. No overlap between any of the tools, so an agent can reliably select the correct one.

    Naming Consistency5/5

    All tools follow the same datacore_ prefix followed by a simple, consistent verb: capture, search, ingest, status, date. The naming pattern is uniform and predictable across the entire set.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a knowledge management utility. Each tool earns its place, covering core operations plus a necessary date utility, and there is no bloat or redundancy.

    Completeness4/5

    The server covers the primary lifecycle of creating and searching notes, with status and date utilities supporting the workflow. Minor gaps include lack of update/delete operations for notes, but the core functionality is solid and agents can work around these limitations.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources