Skip to main content
Glama
QuantumEdu

q-skillvault

Official
by QuantumEdu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to q-skillvault

No user-submitted related servers found.

    Related Servers

    • devbase

      juice094
      A
      license
      Not graded
      quality
      C
      maintenance
      Developer Knowledge OS — local-first bimodal workspace for humans (TUI) and AI agents (MCP). Manage Git repos, vault notes, and assets with 19 MCP tools including unified project context queries.
      AGPL 3.0

    • knowledge-base-server

      Francois0788
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives every AI agent a shared, persistent memory by ingesting Obsidian vaults, code, transcripts, bookmarks and terminal sessions into a three-tier SQLite FTS5 store, then serving token-optimized hybrid retrieval, classification, promotion and cross-source synthesis over MCP and REST. This lets multiple agents read from and write to one compounding brain so each session starts with better context than the last.
      14 npm
      MIT
    • ellmos-homebase-mcp by ellmos-ai

      ellmos-homebase-mcpofficial

      ellmos-ai
      A
      license
      C
      quality
      B
      maintenance
      Enables local-first LLM orchestration with persistent memory, knowledge management, routing, swarm patterns, API probing, tests, automation planning, and plugin discovery via a stdio MCP server, using SQLite for offline storage.
      51
      45 npm
      1
      MIT

    • akatsuki

      fusuyfusuy
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a living systems memory vault to autonomous agents, letting them search notes with BM25 ranking, read sections within token budgets, extract API/port/schema contracts, compute dependency blast radius, and run machine-verifiable invariant assertions before mutating code. It also supports surgical frontmatter edits, schema linting, wikilink integrity checks, and worklog recording, over stdio MCP.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 39 tools

    Disambiguation3/5

    Tools are broadly separated by resource (entries, links, instructions, memories, workflows), but there is real overlap: get_context, get_context_bundle, and vault_mem_context all build agent context; save_entry and save_result both save entries; search_entries and search_by_tags overlap. Descriptions help, but an agent can still hesitate between several similarly scoped tools.

    Naming Consistency3/5

    Most names are readable snake_case, often verb_noun (save_entry, get_entry, list_links, search_instructions). However, conventions are mixed: vault_mem_save puts the verb last with a namespace prefix, while session_wrap, compose_series, route_scenario, and render_workflow use less predictable verb/noun shapes.

    Tool Count2/5

    With 39 tools, the server is clearly overgrown for a single MCP surface, spanning entries, graph refs, versions, workflows, runs, memories, links, instructions, handoffs, artifacts, and projects. This likely exceeds what an agent can comfortably scan and select from without grouping or splitting.

    Completeness3/5

    Entry lifecycle coverage is strong, including save/get/search/archive, versions, restore, graph refs, tags, compare, and context packs. But secondary resources have notable gaps: links and instructions lack update/delete, memories lack update/delete, handoffs have only save/get, and projects have list but no create/update operations.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources