Skip to main content
Glama
alxark

data-filter-mcp

by alxark

Related Servers

Alternatives to data-filter-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for reading, querying, and filtering local JSON files with extended JSONPath syntax, supporting sorting, aggregations, and complex conditions.
      356 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local filesystem MCP server providing constrained file operations (read/write, directory management, search, metadata) within configurable directories, with read-only mode and zero runtime dependencies.
      2 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes a single tool, jq, for running jq filters against JSON files on disk.
      1
      13 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An open-source MCP server bundling 50+ local utility tools for PDF processing, web scraping, OCR, data transformation, and more, with zero configuration and no API keys required.
      51
      102 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A config-driven, zero-dependency MCP server with plugin architecture that enables filesystem operations, shell commands, HTTP requests, and utilities through simple JSON configuration.
      3
      1
      -

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    register_filter clearly creates and validates a new filter, while run_filter and convert_file both execute an existing filter. Their output behaviors (return text vs write a file) are well described, but the shared execution step creates some potential for confusion.

    Naming Consistency5/5

    All three tools follow a consistent snake_case verb_noun pattern: register_filter, run_filter, convert_file. The naming is predictable and easy to scan.

    Tool Count5/5

    Three tools cover the minimal register/run/persist workflow for a custom filter service. The set is tightly scoped, and no tool feels redundant or out of place.

    Completeness4/5

    Core lifecycle operations are present: register a filter, execute it read-only, and execute it with file persistence. Missing list/delete/get-filter operations are minor gaps, partly mitigated by server-side TTL, but an agent cannot explicitly inspect or revoke filters.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues