Skip to main content
Glama
rog0x

schema-tools

by rog0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to schema-tools

No user-submitted related servers found.

    Related Servers

    • Schema Bridge MCP Server

      rafim-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables schema conversion from SQL/Prisma/JSON to Zod, TypeScript, and Pydantic, and generates realistic synthetic mock data.
      3
      MIT

    • apitype

      jayesh-bansal
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to generate TypeScript types, Zod schemas, TypeBox, and JSON Schema from any API endpoint or JSON.
      8 npm
      MIT

    • Trace MCP

      Mnehmos
      A
      license
      A
      quality
      C
      maintenance
      Detects schema mismatches between data producers and consumers through static analysis, supporting extraction, comparison, code generation, and automated validation with watch mode for MCP tools, APIs, and service contracts.
      11
      8 npm
      MIT

    • mcp-jsonschema

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Validates JSON values against JSON Schema (draft-07). Enables schema validation for structured data.
      5 npm
      MIT

    • data-transformer

      tetracoralla
      A
      license
      A
      quality
      B
      maintenance
      Provides safe, deterministic inspection, transformation, validation, and diffing of structured data (JSON, CSV, YAML, Parquet) via schema-aware MCP tools.
      4
      Apache 2.0
    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.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: generation from data, generation from schema, validation, mocking, and diffing. No overlap or ambiguity between tool responsibilities, so an agent should reliably select the correct tool for a given task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (generate_, validate_, mock_, diff_). The verbs are specific and descriptive, and the noun consistently refers to the primary artifact (schema or types). No mixed conventions or vague naming.

    Tool Count5/5

    With exactly 5 tools covering the core schema lifecycle, the count is tight and focused. Each tool earns its place, and the number is within the ideal range for a utility server without being overly minimal or bloated.

    Completeness5/5

    The set covers the major schema operations: creating schemas from data, generating types for coding, validating data, generating mocks, and comparing schemas for evolution. Together they form a coherent, end-to-end toolkit with no obvious dead ends or missing critical operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources