Skip to main content
Glama
knaisoma

data-olympus MCP server

Related Servers

Alternatives to data-olympus MCP server

  • F
    license
    A
    quality
    D
    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.
    11
    AGPL 3.0

TDQS

A4/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have distinct purposes: consult, search, get, gate check, health, event recording, and session recap are clearly separated. However, kb_search and kb_consult both retrieve governing rules, with subtle differences in filtering and when to call, which could cause misselection.

Naming Consistency4/5

The naming follows a consistent 'kb_' prefix with a verb or noun: kb_consult, kb_search, kb_get, kb_health, kb_record_event, kb_session_recap. The exceptions are 'call_tool' and 'tool_search' which break the prefix pattern, but they are meta-tools, so the deviation is minor.

Tool Count4/5

With 9 tools, the count is well within the ideal range. Each tool serves a distinct function in the knowledge base lifecycle. The inclusion of meta-tools (call_tool, tool_search) is slightly unusual but acceptable for a server that may expose a broader tool ecosystem.

Completeness3/5

The tool surface covers reading, searching, consulting, health, and audit recording, but misses direct write/update operations (no create_document, update_document, or delete_document). The server appears to rely on other mechanisms for writes, which is a notable gap for a knowledge base.

Maintenance

ActivityActive
ResponsivenessUnresponsive