Skip to main content
Glama
Sign In
naja-scope

naja-scope

by keplertech
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
      2
      MIT

    • vivado-mcp

      WangErShao
      A
      license
      Not graded
      quality
      D
      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
      A
      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.
      11
      1,531 npm
      63
      Apache 2.0

    • EDA Tools MCP Server

      NellyW8
      A
      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
      ISC

    • 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
      343 PyPI
      68
      GPL 3.0
    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

    A4.2/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool has a sharply distinct purpose, and descriptions explicitly cross-reference siblings (get_drivers vs get_loads vs trace_cone; get_hierarchy vs find vs get_stats vs get_module_card; get_intent vs get_source). Even the potentially overlapping load_intent is disambiguated from the intent=True load flag by explaining it is only for loads that did not retain intent.

    Naming Consistency4/5

    Strong verb_noun convention throughout (get_*, load_*, save_snapshot, reset_universe, open_schematic, annotate_schematic, trace_cone). A few bare verbs/nouns (find, resolve, status) deviate mildly, but they are unambiguous and readable.

    Tool Count4/5

    23 tools is on the heavy side, but this is a genuinely broad EDA surface (five loaders, snapshot lifecycle, connectivity queries, schematic viewer). Each tool earns its place, though the load_* family is the one cluster that could be tightened.

    Completeness4/5

    Covers the full lifecycle: multiple frontends (SV/VHDL/Verilog/Liberty/primitives), session status/reset, snapshot save/load, intent layer, hierarchy/search/resolve, connectivity, stats, source, and schematic interaction. Minor gaps only, such as no export/write-out or per-design unload beyond a full reset, but these are outside the stated read-only analysis scope.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources