Skip to main content
Glama
Bone2510

lasuite-docs-mcp

by Bone2510
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lasuite-docs-mcp

No user-submitted related servers found.

    Related Servers

    • lasuite-docs-mcp

      JonasDoebertin
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP clients such as Claude Code to a self-hosted La Suite Docs instance, letting them full-text search, browse by recency or favorites, read documents as markdown, and create or edit content (including single-section edits). Favorited documents are also exposed as MCP resources so they can be @-mentioned straight into context.
      MIT

    • mcp.office

      gdmkonsult
      F
      license
      Not graded
      quality
      D
      maintenance
      Combined MCP server for Euro-Office DocumentServer enabling Word and PDF editing, document conversion, force-save, session info, and headless prompt-based document editing.
      -

    • paperless-mcp

      baruchiro
      A
      license
      B
      quality
      A
      maintenance
      An MCP (Model Context Protocol) server for interacting with a Paperless-NGX API server. This server provides tools for managing documents, tags, correspondents, and document types in your Paperless-NGX instance.
      44
      1,249 npm
      142
      TypeScript
      ISC
    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

    B3.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create, delete, restore, move, update documents; listing different scopes (all, favorites, trashbin, versions); managing favorites; and user info. No overlapping functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_document, list_favorites, get_document). No deviations or mixed conventions.

    Tool Count5/5

    14 tools are well-scoped for document management, covering CRUD, navigation, versioning, favorites, and trashbin operations. The count fits the 3-15 sweet spot.

    Completeness4/5

    The set covers most core operations, but lacks a dedicated endpoint to retrieve the full document content—only metadata is returned by get_document. Minor gap considering the domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources