Skip to main content
Glama
bmordue

Iterator MCP Server

by bmordue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Iterator MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP JSON Maker

      zb2947244682
      -
      license
      C
      quality
      Not graded
      maintenance
      Enables AI to create, edit, and batch generate JSON data with advanced rule engines. Supports CRUD operations, node-level editing, template management, and multi-format file exports (JSON, JSONL, CSV).
      3
      179 npm
      -

    • Excel Analyser MCP

      contactakagrawal
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables efficient reading, analyzing, and querying of Excel, CSV, and JSON files with support for chunked processing, column/field filtering, and streaming for large datasets. Supports multiple transport protocols (stdio, HTTP, SSE) for flexible integration.
      20 npm
      4
      ISC

    • JSON Mapping & Context MCP

      Bablu-singh
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables schema-aware exploration of JSON data by uploading samples, flattening nested structures, and using heuristic search with token overlap and fuzzy matching to find field paths for target names, accelerating ETL and API onboarding workflows.
      -

    • datamining-skill

      coreworkstr-art
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect and extract data from local CSV, TSV, JSONL and log files far larger than available RAM, using bounded memory, crash-resilient resumable runs, and streamed progress. All file access is confined to user-approved directories, keeping the data private to the machine.
      1
      MIT
    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

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: loading datasets (two separate tools for different formats), navigating records (next, jump, reset), obtaining status, and saving/exporting results. No overlaps or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, using appropriate verbs like get, load, save, export, jump, and reset. The naming convention is uniform and predictable.

    Tool Count5/5

    With 8 tools, the server covers the essential operations for an iterator: dataset loading, record navigation, processing, status tracking, and result export. The count is balanced—neither sparse nor bloated.

    Completeness4/5

    The tool set covers the full lifecycle of iterative processing: loading data (including a variant for jq expressions), navigating (next, jump, reset), saving per-record results, and exporting all results. Missing features like batch operations or record deletion are minor gaps given the server's focused scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources