Skip to main content
Glama
xuio

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ltspice-mcp

No user-submitted related servers found.

    Related Servers

    • macos-control-mcp

      vito1317
      A
      license
      B
      quality
      D
      maintenance
      MCP server that enables AI to fully control macOS — mouse, keyboard, terminal, screenshots, window management, UI element detection, and provides AI-optimized information reporting.
      36
      33 npm
      MIT

    • macos-mcp

      CursorTouch
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight MCP server that bridges AI agents and macOS, enabling automation of file navigation, application control, UI interaction, browser automation, and system operations.
      228
      MIT

    • cua-mac

      ashish200729
      F
      license
      Not graded
      quality
      D
      maintenance
      macOS MCP server that enables AI agents to directly control the host OS, including mouse, keyboard, windows, files, and accessibility automation for computer-use workflows.
      1
      -

    • computer

      hasna
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI agents to control a Mac via screen and mouse/keyboard, supporting Anthropic Claude and OpenAI for task automation.
      236 npm
      Apache 2.0

    • Klyk

      legetdev
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents real OS-level control of macOS, enabling them to click real buttons, type real keys, and observe rendered screens just like a human would.
      44 PyPI
      1
      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

    C2.7/5.0

    Scored across 71 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as multiple ways to create a schematic (createSchematic, createSchematicFromNetlist, createSchematicFromTemplate, createIntentCircuit) and multiple simulation entry points (simulateNetlist, simulateNetlistFile, simulateSchematicFile, runSimulation, queueSimulationJob). Despite detailed descriptions, the high number of similar tools hinders clear disambiguation for an agent.

    Naming Consistency4/5

    Tool names follow a consistent camelCase verb_noun pattern (e.g., getBandwidth, createSchematic, listJobs). There are minor deviations like 'daemonDoctor' and 'autoCleanSchematicLayout', but overall the naming is predictable and consistent.

    Tool Count2/5

    With 71 tools, the server is heavily overloaded. For a domain like circuit simulation, 10-20 tools would be well-scoped. The excessive number implies redundancy and complexity, making it cumbersome for agents to navigate.

    Completeness4/5

    The tool set covers a wide range of tasks: schematic creation, simulation execution, result analysis, job management, UI interaction, and telemetry. There are minor gaps (e.g., lack of a direct 'delete schematic' tool), but overall it is quite complete for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week

    Resources