Skip to main content
Glama
zesun33

@zesun33/mcp-yosys

by zesun33

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_YOSYS_IMAGENoCustom container image to use. Default is localhost/zesun33/asic.localhost/zesun33/asic
MCP_YOSYS_RUNTIMENoRuntime to use: 'podman' (default) or 'host' (use host-installed yosys).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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
yosys_synthesizeA

Synthesizes a Verilog/SystemVerilog design using Yosys, mapping to generic gates, iCE40 FPGA, or Sky130 standard cells, and returns structured cell counts and warnings.

yosys_check_latchA

Performs fast RTL elaboration and latch checking to identify inferred transparent latches, combinational loops, and multiple drivers with exact source lines.

yosys_hierarchyA

Inspects module hierarchy, detecting instantiated submodules and flagging missing/unresolved blackboxes.

yosys_toolchain_infoA

Returns active container/host runtime and version information for the Yosys synthesis engine.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct concern: synthesis, latch/loop checking, hierarchy inspection, and toolchain information. There is no meaningful overlap in purpose or output, so an agent can select the right tool without ambiguity.

Naming Consistency4/5

All tool names share the clear yosys_ prefix and use snake_case, making them predictable. Minor inconsistency exists because some names are verbs (yosys_synthesize), some are verb+noun (yosys_check_latch), and some are nouns (yosys_hierarchy, yosys_toolchain_info), but the pattern is still readable.

Tool Count5/5

Four tools is a well-scoped set for a focused Yosys server. Each tool provides a distinct capability without unnecessary bloat or duplication.

Completeness4/5

The tool set covers the core Yosys workflow: synthesis, latch checking, hierarchy analysis, and environment info. There are minor gaps such as no explicit netlist export or arbitrary Yosys pass execution, but these are not critical for the apparent purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues