Skip to main content
Glama
Sign In
json-to-model

json-to-model

by Ramzanelayodath
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to json-to-model

No user-submitted related servers found.

    Related Servers

    • mcp-api-translator

      krishgok
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that generates MCP servers. Give it an API definition - OpenAPI 3.0/3.1 or a Postman collection or extend an existing server - and it scaffolds a complete, runnable, ownable TypeScript or Python MCP server for that collection of APIs.
      4
      69 npm
      1
      AGPL 3.0

    • MCP Swagger Server

      zecure
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Automatically generates MCP servers from OpenAPI/Swagger specifications, enabling users to interact with any REST API through natural language with flexible endpoint filtering and authentication support.
      -

    • REST API MCP Server

      nifetency
      A
      license
      Not graded
      quality
      D
      maintenance
      A dynamic MCP server that automatically discovers and generates tools from any REST API using OpenAPI/Swagger specifications, enabling instant endpoint access with zero manual configuration.
      21 PyPI
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    C2.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: setup_auth handles authentication, generate_model_from_api performs the core generation, and list_supported_languages provides a utility. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case: setup_auth, generate_model_from_api, list_supported_languages. The naming convention is uniform and predictable.

    Tool Count5/5

    With 3 tools, the set is well-scoped for a focused json-to-model server. Each tool serves a necessary role (auth, generation, languages), and the count falls within the ideal 3-15 range.

    Completeness4/5

    The core generation and prerequisite authentication are covered, and language discovery is useful. However, the server name suggests generating from raw JSON, while the tool only mentions API, so there may be a gap for direct JSON input.

    Maintenance

    ActivityStale
    ResponsivenessSyncing

    Resources