Skip to main content
Glama
dexio-wiki

Dexio

by dexio-wiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Dexio

No user-submitted related servers found.

    Related Servers

    • wikicore

      carlaost
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to build and maintain a shared, git-backed Markdown wiki: they search, file, update and link notes with YAML frontmatter, keep verbatim sources, and optionally read code repos, so knowledge one assistant records is available to all the others. Runs without LLM calls, embeddings or a database, with the vault's own files defining page types, instructions and tools.
      MIT

    • vault-mcp

      Lincyaw
      A
      license
      A
      quality
      D
      maintenance
      Markdown + SQLite knowledge store with bidirectional wikilinks, exposed as an MCP server for AI agents to maintain an interconnected knowledge base.
      11
      MIT

    • compound-memory

      chinwe
      A
      license
      A
      quality
      A
      maintenance
      Enables multiple AI agents on one machine to write, search, fetch, link, and give feedback on a shared local store of Markdown-backed facts, preferences, and conventions that persists across sessions. Memories gain confidence as different hosts confirm their use and can be distilled into denser ones, so agents stop re-discovering the same context.
      5
      598 PyPI
      1
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target a distinct resource+action: page CRUD (read/write/edit/append/delete/move), file ops, search, history, health, visibility. The main overlap is write_page vs edit_page vs append_page, which the descriptions clarify (whole replace, partial, end-append), and change_pages explicitly reframes those same operations as a batch, so boundaries are mostly clear but require reading.

    Naming Consistency4/5

    Almost all names follow a consistent snake_case verb_noun pattern (list_pages, read_page, write_page, edit_page, delete_page, move_page, upload_file, set_visibility). Minor deviations are the noun-only names wiki_health and page_history, which still fit the vocabulary and remain readable.

    Tool Count4/5

    16 tools is slightly above the ideal band but well-scoped for a full wiki: page lifecycle, file handling, search, history, health, batch changes, and visibility each earn their place. No redundant or trivial tools inflate the count.

    Completeness4/5

    Strong lifecycle coverage: read/write/edit/append/delete/move pages, upload/delete/list files, search, revision history, health checks, batch changes, and visibility control. Minor gaps exist (no explicit page-restore or file rename/move tool, and file read is folded into read_page), but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources