Skip to main content
Glama
Sign In
personal-kg-mcp

personal-kg-mcp

by tomschell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to personal-kg-mcp

No user-submitted related servers found.

    Related Servers

    • Inficy

      artnames
      A
      license
      Not graded
      quality
      C
      maintenance
      Captures AI agent runs and turns them into tamper-evident execution records showing tool use, timing, failures, recoveries, and human interventions. Records can be inspected, exported, and verified offline.
      MIT

    • Worktrail

      jasonethicseo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to record and resume engineering work as durable, byte-exact threads of focus, decisions, evidence, and next steps.
      4
      Functional Source , Version 1.1, ALv2 Future
    • Mandrel

      Mandrelofficial

      RidgetopAi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to maintain structured, persistent memory as a typed-edge knowledge graph over contexts, decisions, and tasks, with deterministic auto-threading, trust signals, and replayable story recall. It also exposes a token-lean MCP gateway for on-demand tool discovery, helping agents preserve causal project context across sessions.
      4,741 npm
      5
      MIT

    • MCP Workflow Tracker

      Aceek
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides observability for multi-agent workflows by tracking hierarchical task structure, architectural decisions, reasoning, encountered problems, code modifications with Git diffs, and temporal metrics.
      44 npm
      MIT
    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.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists: kg_search, kg_query_context, and kg_get_relevant_context all retrieve information in different ways, and kg_capture vs kg_capture_session have similar names. The detailed descriptions help disambiguate, but an agent could still misselect between context retrieval tools.

    Naming Consistency3/5

    All tools share the 'kg_' prefix, but the naming pattern is mixed: some are verb_noun (kg_list_tags, kg_update_node), some are bare verbs (kg_capture, kg_search), and some are noun-based unified tools (kg_edges, kg_admin, kg_node). This inconsistency makes the set feel less predictable, though the prefix provides a common thread.

    Tool Count4/5

    With 17 tools, the server is slightly above the ideal range of 3-15, but the count is reasonable for a personal knowledge graph managing nodes, relationships, sessions, questions, and admin operations. The tools collectively cover a broad domain without being excessive.

    Completeness5/5

    The tool surface covers the full lifecycle: creation (kg_capture), retrieval (kg_search, kg_node get), update (kg_update_node), deletion (kg_node delete), plus relationship management, session handling, question tracking, project state, admin, and diagnostics. No obvious gaps prevent an agent from performing core knowledge graph operations.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources