Skip to main content
Glama
Sign In
atlas-brief-mcp

atlas-brief-mcp

by drproof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to atlas-brief-mcp

No user-submitted related servers found.

    Related Servers

    • compendio-mcp

      RuloGB
      A
      license
      A
      quality
      B
      maintenance
      Indexes your project's markdown documentation and exposes it to AI agents via local hybrid search (lexical + semantic) with progressive disclosure tools.
      3
      115 npm
      5
      MIT

    • docdex

      bekirdag
      A
      license
      Not graded
      quality
      B
      maintenance
      Docdex is a lightweight, local documentation indexer/search daemon. It runs per-project, keeps an on-disk index of your markdown/text docs, and serves top-k snippets over HTTP or CLI for any coding assistant or tool—no external services or uploads required.
      1,185 npm
      16
      MIT
    • semlith

      semlithofficial

      semlith
      A
      license
      C
      quality
      A
      maintenance
      Local search over your code and documents for AI agents. Hybrid search and a code graph over your code and documents (PDF, Word, PowerPoint, Excel, EPUB), served over MCP with file and line spans, from one Rust binary on your machine.
      2
      8
      10
      Apache 2.0

    • Agent Memory Engine

      ululazmi18
      A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents to query a fully local SQLite FTS5 memory index of a codebase, returning high-density identity cards with exact line references, AST symbol contracts, phase maps, and colloquial intent search so agents can work without scanning raw files. It also supports incrementally syncing code changes and enriching knowledge under a six-pillar quality gate, keeping everything on-device with no cloud leakage.
      5
      MIT

    • litedocs-mcp

      gowthamraj07
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search a local folder of Markdown, AsciiDoc, and text files through a SQLite FTS5 keyword index, returning the most relevant sections with file paths, line ranges, and heading breadcrumbs instead of grepping through a repo. It also exposes tools to list indexed documents and refresh the index incrementally, all offline with no dependencies, network calls, or embeddings.
      3
      MIT

    • docs-mcp

      kage1020
      F
      license
      Not graded
      quality
      D
      maintenance
      Indexes documentation sites by base URL and serves keyword search, optional semantic search, and Markdown page retrieval as MCP tools, all from a single SQLite file.
      -
    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 15 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (read vs outline, status vs tasks, set_status vs publish, sheet_update vs sheet_append), and descriptions explicitly cross-reference when to use each alternative. The only genuine overlaps are atlas_where vs atlas_search (both BM25 lookups over the same index) and atlas_status vs atlas_tasks, but the descriptions disambiguate those well enough that misselection is unlikely.

    Naming Consistency4/5

    All names use a consistent snake_case with the atlas_ prefix, which is the strongest consistency signal here. There is minor variation in convention—some are verb-first (atlas_read, atlas_publish, atlas_set_status), others noun-first (atlas_status, atlas_tasks, atlas_sheets), and subresource ordering differs (atlas_code_find vs atlas_sheet_update)—but the pattern stays readable.

    Tool Count5/5

    Fifteen tools is well within a healthy scope for a documentation/project-memory server and each maps to a distinct capability (search, read, outline, links, tasks, status, brief, publish, status flip, lint, code find, and three sheet operations). Nothing feels redundant or padded.

    Completeness4/5

    The documentation lifecycle is thoroughly covered: discover (where/search/outline), inspect (read/links/tasks/status), act (brief/publish/set_status), plus code lookup and lint. Minor gaps remain—there is no spreadsheet cell/row read tool (only list/update/append) and no delete operations for Work Orders or rows—but these are workaroundable and do not block core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources