Skip to main content
Glama
najaeda

naja-scope

by najaeda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to naja-scope

No user-submitted related servers found.

    Related Servers

    • WaveQ

      IshaanDugar
      A
      license
      A
      quality
      C
      maintenance
      Local MCP server for querying VCD waveform files via SQLite; enables AI agents to ask precise questions about signal values, transitions, and clock cycles without dumping raw VCD text.
      18
      1
      MIT

    • vivado-mcp

      WangErShao
      A
      license
      Not graded
      quality
      C
      maintenance
      A lean MCP server that lets AI agents drive Xilinx Vivado for synthesis, implementation, simulation, and diagnostics through 30 curated tools and raw Tcl execution.
      Apache 2.0

    • Universal Netlist MCP Server

      IntelligentElectron
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI agents to understand and analyze electrical schematics from Cadence and Altium for comprehensive design reviews through natural conversations.
      267 npm
      49
      Apache 2.0

    • EDA Tools MCP Server

      NellyW8
      F
      license
      A
      quality
      F
      maintenance
      A comprehensive Model Context Protocol server that connects AI assistants to Electronic Design Automation tools, enabling Verilog synthesis, simulation, ASIC design flows, and waveform analysis through natural language interaction.
      6
      112
      -

    • ltspice-mcp

      Cognitohazard
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that connects LLM assistants to real circuit simulation: LTspice and ngspice, plus direct editing of LTspice .asc schematics. Simulation results come back as structured numbers so the assistant can design, verify, and iterate on circuits.
      48
      51
      GPL 3.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.1/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: per-language/level loaders, session lifecycle, hierarchical/name/connectivity queries, source/intent retrieval, and schematic interaction. Descriptions explicitly cross-reference alternatives (e.g., resolve vs find, get_drivers vs get_loads vs trace_cone), so no two tools appear interchangeable.

    Naming Consistency4/5

    Most names follow a predictable snake_case pattern with clear families: load_*, get_*, and action_* (save_snapshot, open_schematic, annotate_schematic, trace_cone). However, single-word names like resolve, find, and status break the dominant verb_noun convention, keeping it from a perfect score.

    Tool Count3/5

    At 23 tools, the surface is heavy for the typical 3–15 sweet spot. Although each tool maps to a distinct EDA workflow, the seven load_* variants in particular make the set feel borderline oversized and invite consolidation.

    Completeness4/5

    The set covers loading multiple HDL/model formats, session lifecycle (status, reset, save/load snapshot), hierarchy and name search, connectivity tracing, source/intent retrieval, and schematic interaction. Only minor gaps exist, such as no direct enumeration of assign glue or snapshot deletion/listing.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources