Skip to main content
Glama
circuitry-dev

Circuitry MCP Server

Official
by circuitry-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Circuitry MCP Server

No user-submitted related servers found.

    Related Servers

    • PLCs.ai MCP Server

      PLCsai
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to Allen-Bradley, Siemens, and CODESYS PLC projects for discovering, asking questions about, analyzing, and proposing code changes, with access to live tag values and version exports under permission-scoped controls.
      -
    • HiveFlow MCP Server by hiveflowai

      HiveFlow MCP Serverofficial

      hiveflowai
      A
      license
      B
      quality
      C
      maintenance
      Connects AI assistants (Claude, Cursor, etc.) directly to the HiveFlow automation platform, allowing them to create, manage, and execute automation flows through natural language commands.
      9
      10 npm
      4
      MIT

    • Flowchart MCP

      Zafer-Liu
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create, edit, and export flowcharts through a local web-based editor with visual drag-and-drop, real-time sync, and 14 MCP tools for full node/edge CRUD.
      2
      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.2/5.0

    Scored across 134 tools

    Disambiguation3/5

    The tool set has clear domains (e.g., codebook, nodes, sheet, layout), but there is significant overlap within domains that could confuse an agent. For example, codebook.addCell and code.create/text.create/sheet.create have overlapping purposes depending on context, and sheet.* vs. spreadsheet.* tools have similar functionalities but target different document types. Descriptions help clarify, but the boundaries are not always distinct.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern with dot notation for namespacing (e.g., codebook.addCell, nodes.delete, layout.createSection). All tools use snake_case consistently, and naming conventions are predictable across the entire set, making it easy to infer functionality from names.

    Tool Count2/5

    With 134 tools, the count is excessive for the server's purpose of interacting with Circuitry's workflow and design features. This many tools creates a steep learning curve and likely includes redundant or overly granular operations that could be consolidated, such as multiple sheet and spreadsheet tools with similar functions. A more focused set of 20-40 tools would be more appropriate.

    Completeness5/5

    The tool surface is exceptionally complete, covering CRUD/lifecycle operations for all major domains (e.g., nodes, edges, code, sheets, layout, screens). It includes comprehensive workflows from connection management to execution, design, and documentation, with no apparent gaps that would cause agent failures. The tools support everything from basic creation to advanced analysis and fixes.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources