Skip to main content
Glama
knaisoma

data-olympus MCP server

Related Servers

Alternatives to data-olympus MCP server

  • F
    license
    A
    quality
    C
    maintenance
    Automatically organizes and merges learned CS knowledge into a graph structure using Claude for entity/relation extraction and SQLite for storage, with tools for ingestion, querying, merging, and managing nodes and edges.
    6
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    A local OKF-compatible knowledge engine for AI agents. Enables capturing agent conversations, hybrid semantic+keyword search, MCP serving to agents, interactive graph visualization, and OKF bundle export.
    Apache 2.0

Related Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server for a Markdown-backed knowledge repository, offering tools for searching, retrieving, validating, and authoring records, plus MCP Apps that render dashboards and inline tables in compatible clients.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP server that gives AI coding agents a git-backed markdown wiki to read and update, enabling search, read, write, verify, ingest, promote, and lint operations on versioned knowledge documents with schema validation, staleness tracking, and contradiction detection.
    4
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    An MCP server that enables verified agents to retrieve from, propose changes to, and share capabilities around a human-owned Markdown/Git knowledge base, ensuring curation, exact-byte approval, and Git-based promotion.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to maintain a persistent Markdown knowledge base by ingesting sources, searching and reading notes, and creating or updating wiki pages with optimistic locking.
    12
    AGPL 3.0

TDQS

A4/5.0

Scored across 9 tools

Disambiguation4/5

Each tool has a fairly distinct role and the descriptions explicitly contrast the closest pairs (kb_get vs kb_search by id vs topic; kb_consult vs kb_gate_check for proactive reading vs per-action verdict; tool_search discovers, call_tool executes). The only mild overlap is consult/gate_check, both of which concern governing-rule compliance, but the guidance for when to use each is explicit.

Naming Consistency4/5

Seven tools share a clean kb_ prefix with predictable verb/verb_noun forms (kb_get, kb_search, kb_consult, kb_gate_check, kb_health, kb_record_event, kb_session_recap). The two meta-tools (call_tool, tool_search) break the prefix scheme and call_tool is a notably generic name, but overall style is consistent snake_case.

Tool Count5/5

Nine tools is well within a healthy scope for a knowledge-base/governance server, and each named tool maps to a distinct operation (retrieve, search, consult, gate, health, audit-write, recap, plus dynamic discovery/execution). No tool feels like filler.

Completeness2/5

Several tools explicitly point to operations that are absent from the surface: kb_record_event tells agents to read events back via kb_audit or kb_compliance, kb_search references kb_curate, and kb_session_recap references 'kb pending' — none of which exist here. There is also no document write/curation or status-remediation tool, so the pending_actions maintenance loop the server advertises cannot actually be closed.

Maintenance

ActivityActive
ResponsivenessUnresponsive