Skip to main content
Glama
nahuelgallo

ultimate-construct3-mcp

by nahuelgallo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ultimate-construct3-mcp

No user-submitted related servers found.

    Related Servers

    • renpy-mcp

      teast1234
      A
      license
      A
      quality
      C
      maintenance
      This MCP server enables AI agents to act as native Ren'Py visual novel development assistants, covering code reading and writing, offline documentation search, compilation and lint verification, automatic bug fixing, asset management, save handling, and translation diagnostics. It lets agents inspect project labels and references, inject code, run SDK commands, and repair common issues such as return values, missing from clauses, BOM inconsistencies, stale saves, and incomplete translation blocks.
      19
      MIT

    • mcdev-mcp

      use-ai-for-mc
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that empowers AI coding agents to work effectively with Minecraft mod development, providing static analysis of decompiled source code and runtime interaction with a running Minecraft instance.
      31
      25 npm
      16
      MIT

    • GMS2 MCP Server

      Atennebris
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that parses GameMaker Studio 2 projects, providing developers and AI agents with quick access to project structure, GML code, and asset metadata.
      19
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct facet of the docs surface (search, browse topics, browse categories, fetch topic, ACE reference, examples). The only mild overlap is between search_docs and get_examples, since both are query-style lookups, but the example-specific description makes the boundary clear enough.

    Naming Consistency5/5

    All names follow a clean verb_noun snake_case pattern (search_*, list_*, get_*), with verbs matching the operation type. No mixed conventions.

    Tool Count5/5

    Six tools is a well-scoped set for a documentation lookup server — one query tool, one content fetcher, two browsing tools, plus ACE and example lookups. Each earns its place without redundancy.

    Completeness4/5

    The surface covers the full docs workflow: browse categories/topics, search, fetch full content, and specialized ACE/example lookups. Minor gaps exist (e.g. no versioned docs or plugin-name discovery for ACE), but agents can work around them via search.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources