Skip to main content
Glama
Sign In
gowin-mcp

gowin-mcp

by Papipapito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gowin-mcp

No user-submitted related servers found.

    Related Servers

    • fpgaZeroMCP

      lcapossio
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for FPGA toolchain operations including linting, simulation, synthesis, place-and-route, bitstream programming, and IP core registry via GitHub.
      25
      8
      MIT

    • vivado-mcp-agent

      wangyuxin0707
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for deterministic Vivado FPGA automation including project scaffolding, simulation, synthesis, implementation, and gated bitstream generation.
      4
      MIT

    • Coverity

      kriomant
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      MCP server for Blackduck Coverity Static Analysis Software.
      -

    • verilator-mcp

      chinn-choppa
      A
      license
      C
      quality
      B
      maintenance
      Provides a portable local MCP interface for RTL simulation, diagnostics, and verification workflows with Verilator, currently exposing server information, tool discovery, and bounded text diagnostic parsing while lint and simulation execution remain planned.
      3
      Apache 2.0
    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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct artifact or question: build discovery, headline summary, resources, timing, comparison, pins, warnings, and a CI gate. The main soft overlap is gowin_summary versus gowin_resources/gowin_timing, and gowin_check versus gowin_timing, but the descriptions explicitly position summary as the entry point and check as the pass/fail gate, which resolves most confusion.

    Naming Consistency4/5

    All tools share a consistent gowin_ prefix and snake_case, with predictable domain nouns (resources, timing, pins, warnings, summary). A few names use verb forms (check, list_builds, compare) while others are bare nouns, a minor deviation that does not harm readability.

    Tool Count5/5

    Eight tools is well-scoped for an FPGA build-analysis server: one discovery tool, four detail views, one diff, one log/pin reader, and one CI gate. No tool feels redundant or missing at this scale.

    Completeness4/5

    The surface covers the full read-only analysis lifecycle: find builds, summarize, drill into resources/timing/pins, compare builds, triage warnings, and gate CI. Gaps are minor, e.g. no tool to dump raw report/log files or inspect the .sdc directly beyond what summary reports.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources