Skip to main content
Glama
alxark

data-filter-mcp

by alxark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to data-filter-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-json-reader

      oovz
      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.
      15 npm
      2
      MIT

    • paddock

      JohnXu22786
      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

    • jq-mcp

      kolodny
      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
      7 npm
      MIT

    • Kitbag MCP

      syedtaj7
      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
      58 npm
      MIT

    • Modular MCP Server

      0brym
      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
      -
    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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a unique and clearly defined purpose: register_filter validates and stores a filter, run_filter executes it on a file and returns text, and convert_file executes and saves the result to a file. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (register_filter, run_filter, convert_file), making the API predictable and easy to navigate.

    Tool Count4/5

    With only 3 tools, the server is minimal but well-scoped for its purpose of applying custom filters to files. The count is appropriate for a focused utility, though additional management tools (e.g., list_filters) could be added without bloat.

    Completeness4/5

    The tools cover the essential workflow: register a filter, run it (in-memory output), and convert it (persisted output). Missing are filter listing, deletion, or inspection, but the automatic expiration mitigates the need for explicit management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources