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.
    3
    AGPL 3.0

TDQS

A4.2/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search, health check, get by ID, session recap, consultation recording, gate checking, audit event writing, and tool meta-operations. No two tools overlap in functionality; the detailed descriptions reinforce the boundaries.

Naming Consistency5/5

All tools follow a consistent lowercase snake_case pattern with a category prefix: kb_* for knowledge-base operations and tool_*/call_* for tool meta-operations. The verb-noun structure (search, get, consult, check, record) is uniform and predictable.

Tool Count5/5

Nine tools is within the optimal range for a knowledge-base server with governance features. Each tool serves a specific role without redundancy, and the count feels appropriate for the server's scope.

Completeness3/5

The core workflow—search, retrieve, consult, gate-check, and record events—is covered, but the description of kb_record_event explicitly references kb_audit and kb_compliance as read-back tools that are not present in the server. This leaves a notable gap for agents needing to review audit history.

Maintenance

ActivityActive
ResponsivenessUnresponsive