mcp-gds
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_GDS_RUNTIME | No | Execution runtime for tools. Set to 'host' to force host binaries instead of container (Podman) execution. | podman |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gds_infoA | Reads GDSII/OASIS layout metadata headlessly (cells, top cells, bounding boxes, per-layer shape counts). Pure introspection, no PDK needed. Use when you need to know what is inside a layout file. |
| gds_stream_outA | Streams a DEF layout to GDSII via headless KLayout using Nangate45 LEFs (abstract cell footprints; full transistor GDS needs the PDK). Use to produce DRC input or handoff previews, not tapeout signoff. |
| drc_klayoutA | Runs KLayout batch DRC on a GDS file. Default is a generated generic width/space smoke deck over the layout's own layers (geometry sanity, not foundry signoff). Pass deck_file for a real PDK rule deck. Does not do LVS; use lvs_netgen for netlist comparison. |
| lvs_netgenA | Compares two SPICE netlists with Netgen batch LVS and reports match/mismatch with net/device counts. Compares netlists only; use extract_magic to derive a layout netlist first. Does not do DRC. |
| extract_magicA | Extracts a SPICE netlist from layout with Magic batch mode (ext2spice lvs). Runs on generic technology: correct flow plumbing, but device-accurate extraction needs a PDK tech file. |
| gds_toolchain_infoA | Returns active container/host runtime and versions of KLayout, Magic, and Netgen. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: metadata reading, DEF-to-GDS conversion, DRC, LVS, extraction, and version info. No overlapping or ambiguous responsibilities.
Names generally follow a predictable pattern, but mix domain-first (gds_info, gds_stream_out) with verb-first (extract_magic) and tool-specific suffixes (drc_klayout, lvs_netgen). Slightly inconsistent but still mostly intuitive.
Six tools cover the essential operations for a layout-to-signoff verification workflow without redundancy or overload. The count feels well-scoped.
The set covers the main EDA flow steps (metadata, conversion, DRC, LVS, extraction, environment info). Minor gaps like a dedicated netlist viewer or layout manipulation tool could be added, but the core cycle is complete.