Skip to main content
Glama

Related Servers

Alternatives to tela

  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    This is a connector to allow Claude Desktop (or any MCP client) to read and search any directory containing Markdown notes (such as an Obsidian vault).
    990 npm
    1,352
    AGPL 3.0
  • A
    license
    A
    quality
    A
    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
    12
    18,541 PyPI
    4,452
    AGPL 3.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    A token-optimized MCP server for Notion that reduces context window usage by 73% while preserving full functionality, enabling AI assistants to interact with Notion efficiently.
    9 npm
    2
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI apps like Claude, ChatGPT, Copilot, Claude Code and Codex to read and write a shared company wiki over MCP, where meetings, work sessions and notes become living pages about people, projects and decisions. It also serves search, briefs, transcripts, decisions and action items, and lets teams connect their own git-hosted team wiki.
    1
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Self-hosted enterprise knowledge hub that compiles organizational docs into a structured wiki and serves it to AI clients via MCP with fine-grained access control.
    1
    1,517
    -
  • A
    license
    Not graded
    quality
    A
    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.
    2,986 npm
    80
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Local-first personal wiki and memory server for AI agents. MCP clients can capture knowledge, retrieve context, read and maintain source-backed wiki pages, and carry project context between sessions.
    33
    92
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    A machine-local, agent-writable knowledge base MCP server that lets coding agents autonomously record and retrieve hard-won operational facts, incidents, and corrections as markdown pages in a git repo, with provenance, talk pages, and search.
    4 npm
    MIT
  • 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

TDQS

A3.8/5.0

Scored across 50 tools

Disambiguation4/5

The server has many overlapping retrieval and authoring tools (search/fetch/research/get_page/read_chunk; preview/lint page vs deck), but the descriptions explicitly differentiate each with cross-references and preferred-tool guidance. A few boundaries remain thin, such as fetch vs get_page compatibility aliasing and the multi-step attachment upload flow, so not every tool is instantly separable.

Naming Consistency4/5

Nearly all names are snake_case and many follow a verb_noun pattern (list_pages, create_space, delete_attachment), with a consistent atlas_ prefix for the doc-generation subgroup. The main deviations are noun-phrase guide/utility tools (deck_authoring_guide, knowledge_gaps, fetch), so the convention is readable but not perfectly uniform.

Tool Count1/5

At 50 tools, the surface is far beyond the typical 3-15 well-scoped range and is an extreme mismatch for a single MCP server, even accounting for the broad wiki/deck/sheet/Atlas scope. Several areas could be consolidated, such as the three-step attachment upload flow, separate guide fetches, and fetch/get_page overlap.

Completeness4/5

The surface covers page/space/comment/attachment/share/revision lifecycles plus authoring guides, lint/preview, decks, sheets, research, and Atlas doc generation, which is very broad. A few lifecycle gaps remain, such as no delete_comment, no restore-page operation, and limited attachment metadata editing, so it is not quite a dead-end-free surface.

Maintenance

ActivityActive
ResponsivenessSlow