Skip to main content
Glama
Sign In
folio

folio

by jakubro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to folio

  • basic-memory

    basicmachines-co
    A
    license
    A
    quality
    B
    maintenance
    Basic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md
    2
    12
    19,662 PyPI
    4,519
    AGPL 3.0

  • my-memory

    PabloPC05
    A
    license
    Not graded
    quality
    B
    maintenance
    Serves a git-backed folder of Markdown notes over MCP so AI agents can search, read, write, move and delete them, with every write recorded as a git commit attributed to the calling client. Supports full-text section search with snippets, wikilinks and typed relations, LFS-backed searchable attachments, optimistic concurrency for multiple agents, and per-client token or OAuth 2.1 access.
    Apache 2.0

  • OKF Wiki

    ysasiwat
    A
    license
    Not graded
    quality
    B
    maintenance
    Serves folders of an Obsidian vault to AI agents over MCP as Open Knowledge Format bundles, letting them browse, search, read, graph and write draft notes with recorded provenance and checkable trust. Agents can propose changes, but only the user approves them, and stale or externally edited content is flagged rather than trusted.
    Apache 2.0

Related Servers

  • folio

    evergreen-it-dev
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server built into Folio, an open-source self-hosted team wiki where pages are Markdown files in your Git repository. Agents search, read, create and edit pages, tables and boards with the same access rights as people, over OAuth or a personal token.
    3,721 npm
    82
    MIT

  • graphiti-folder

    notx2wice
    A
    license
    A
    quality
    D
    maintenance
    A read-only MCP server that lets you search current and historical facts from a time-indexed knowledge graph derived from a folder of Markdown/text documents, with verification against original sources. It exposes tools for status, fact search, history search, and revision lookup while keeping document insertion and modification to the CLI.
    3
    MIT

  • cc-dash

    AntJanus
    A
    license
    Not graded
    quality
    B
    maintenance
    A local dashboard and Model Context Protocol server for managing a multi-project portfolio whose entire state lives in markdown files.
    MIT

  • DocGraph

    Detective-XH
    A
    license
    A
    quality
    C
    maintenance
    MCP server that indexes Markdown, Word, HTML, and PDF documents into a SQLite knowledge graph with CJK+Latin full-text search and cross-document reference tracking. Runs drift audits to surface stale policies, conflicting research claims, superseded ADRs, and undocumented code exports.
    10
    9
    MIT

  • kmd

    bartolli
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for structured markdown knowledge vaults that provides validation, FTS5 search, and wikilink cross-references. Enables AI agents to prime context and search across vaults using two MCP tools and template resources.
    8
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 16 tools

Disambiguation4/5

Most tools are clearly distinct, and descriptions actively disambiguate near-neighbors by naming the alternative ('for what changed of what the reader read use folio_changes, and for one document's versions folio_history'). There are nonetheless two overlapping clusters — folio_changes/folio_digest/folio_history/folio_reads (what changed or was read) and folio_health/folio_needs/folio_stale (what is wrong or needs attention) — plus folio_query vs folio_embed, which an agent must read closely to separate.

Naming Consistency5/5

Every tool uses the identical folio_ prefix followed by a single lowercase noun, with no camelCase or verb-style outliers anywhere in the set. The pattern is fully predictable, so an agent can reliably guess and remember names.

Tool Count4/5

At 16 tools the surface sits just above the comfortable range, but the domain is genuinely broad (reading state, provenance, embeddings, health, history, digests, impact analysis) and each tool maps to a distinct capability rather than a variant of another. A couple of the analysis tools could plausibly be folded together, but nothing is filler.

Completeness4/5

The read/analysis lifecycle is well covered: discovery, per-document structure, provenance, data querying, semantic relations, health, change tracking, history, and impact analysis before edits. The notable gap is that there are no mutation tools at all — no create/update/move — so writing is left to external file editing, which the descriptions implicitly assume ('use it after editing documents').

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources