Skip to main content
Glama
Sign In
levuvo-nextcloud-mcp

levuvo-nextcloud-mcp

by peterkarlhuber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to levuvo-nextcloud-mcp

No user-submitted related servers found.

    Related Servers

    • local-tools-mcp-server

      fenhuayue
      F
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.
      4
      -

    • FileManager MCP Server

      Surf-Team
      F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for AI clients to browse and search project files securely, with configurable permissions, virtual paths, and key-based access.
      -

    • Local Knowledge MCP

      TuanLe-bk18
      A
      license
      Not graded
      quality
      B
      maintenance
      A security-first, read-only MCP server that lets clients browse and read text, PDF, and XLSX files from an explicit allowlist of local folders, with strict path and secret protections.
      MIT

    • Home File Agent

      nfedunwork-code
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides secure read-only access to a local folder, enabling file listing, reading, semantic search (RAG), and indexing status via natural language, integrated with Claude Desktop and a custom agent loop.
      -
    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 4 tools

    Disambiguation5/5

    Each tool maps to a distinct operation: browsing directories (list_files), metadata only (get_file_info), content extraction (read_file) and name search (search_files). The descriptions explicitly cross-reference each other with guidance like 'use get_file_info for metadata' and 'for metadata use get_file_info', and error messages redirect to the correct tool.

    Naming Consistency5/5

    All four names follow a strict verb_noun snake_case pattern: read_file, list_files, get_file_info, search_files. Prefixes ('file' vs 'files') differ only to reflect resource cardinality, which is still predictable.

    Tool Count4/5

    Four tools is on the thin side, but for a read-only, share-scoped Nextcloud file surface each one covers a distinct need (navigate, inspect, read, find). Nothing is redundant and nothing obvious is missing from the navigation/read workflow.

    Completeness4/5

    The read-only lifecycle is fully covered: browse shares/folders, inspect metadata, search by name, and read paginated content across many formats. Gaps are minor and intentional (no write/upload/delete, no full-text search inside documents, no binary download), all of which are explicitly stated limitations rather than dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources