Skip to main content
Glama
sammcj

mcp-data-extractor

by sammcj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-data-extractor

No user-submitted related servers found.

    Related Servers

    • SNAP MCP Server

      MnkyBr8n
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that parses code, documents, data, and config files into structured database snapshots for targeted AI retrieval, enabling code analysis and project understanding via LLM interactions.
      1
      -

    • Basic MCP Server

      Merlin21x
      F
      license
      B
      quality
      D
      maintenance
      A basic TypeScript implementation of the Model Context Protocol (MCP) server designed as a starting point for MCP development. Provides a minimal foundation for building custom MCP servers with stdio configuration for local integration with VS Code and GitHub Copilot.
      1
      -

    • Refactor MCP

      egn88
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for automated refactoring of Java and TypeScript/JavaScript codebases.
      16
      4
      -

    • CRAG-MCP

      bluemot
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that builds and queries a config-aware code graph with support for conditional compilation (#ifdef) filtering, enabling context-aware code analysis across different build configurations.
      9
      -

    • Swagger MCP Server

      tuskermanshu
      A
      license
      B
      quality
      D
      maintenance
      A server based on Model Context Protocol that parses Swagger/OpenAPI documents and generates TypeScript types and API client code for different frameworks (Axios, Fetch, React Query).
      12
      11 npm
      16
      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

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly distinct extraction types: structured data (e.g. i18n translations) versus SVG components. An agent can easily choose between them based on the file/content type, with no meaningful overlap.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern: extract_data and extract_svg. The naming is simple, predictable, and directly reflects the output type.

    Tool Count4/5

    At two tools, the server is slightly below the typical well-scoped range, but the count is reasonable for a narrowly focused extractor utility. Each tool covers a distinct extraction workflow and earns its place.

    Completeness4/5

    The server covers its stated domain reasonably well: data extraction and SVG extraction are both implemented with source-replacement behavior. It is a small surface, but there are no obvious dead ends within the apparent scope of a specialized extractor.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources