Skip to main content
Glama
Solitario119

IC-CAP MCP Server

by Solitario119
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to IC-CAP MCP Server

No user-submitted related servers found.

    Related Servers

    • qucs-mcp

      leonardoAB1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents to generate Qucs circuit schematics, run simulations, and parse results programmatically.
      1
      MIT

    • COMSOL MCP Server

      HBPEKING-TKS
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.
      78
      MIT

    • comsol-mcp-server

      Qwup2112
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization via the MCP protocol.
      MIT

    • mcp-gds

      zesun33
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to run GDSII stream-out, KLayout DRC, Netgen LVS, and Magic extraction via MCP.
      6
      34 npm
      Apache 2.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

    B3.4/5.0

    Scored across 128 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Even with many similar getters/setters for different object types, the prefixes (mvar, dvar, svar, etc.) disambiguate them. Convenience wrappers like input_M/S/B are explicitly documented as equivalents to input_get_data with different msb flags, avoiding confusion.

    Naming Consistency5/5

    Naming follows a consistent snake_case verb_noun pattern with object-type prefixes (object_, model_, dut_, setup_, input_, output_, transform_, plot_, macro_, mvar_, etc.). All tools adhere to this convention, with occasional compound names like 'object_get_fullname' and 'iccap_job_cancel' that still fit the pattern.

    Tool Count2/5

    128 tools is far above the 25+ threshold for 'too many'. While IC-CAP is a complex domain requiring many operations, the sheer number overwhelms the agent's ability to select the right tool efficiently, risking misselection and cognitive overload.

    Completeness5/5

    The tool surface appears comprehensive for the IC-CAP domain: it covers creation, deletion, renaming, copying, inspection, and execution for all major object types (Model, DUT, Setup, Input, Output, Transform, Plot, Macro, variables, parameters). It also includes simulation, measurement, data import/export, session management, job control, and error handling, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources