Skip to main content
Glama
Papipapito

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
      B
      maintenance
      An MCP server for FPGA toolchain operations including linting, simulation, synthesis, place-and-route, bitstream programming, and IP core registry via GitHub.
      25
      7
      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.
      -

    • mcp-kicad-sch-api

      circuit-synth
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for creating, modifying, and analyzing KiCAD schematic files using natural language.
      21
      MIT
    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.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 issues

    Resources