Schema | mcp-verilog

mcp-verilog

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_VERILOG_RUNTIME`	No	Set to 'host' to force host binaries instead of container execution.	podman

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
verilog_lintA	Lints Verilog / SystemVerilog source files using verible-verilog-lint and returns structured line, column, severity, and rule diagnostics.
verilog_compileA	Performs syntax validation and elaboration checking on Verilog files using iverilog or verilator without running full simulation.
verilog_simulateA	Compiles and runs a behavioral testbench simulation using iverilog + vvp. Captures runtime assertions ($fatal), testbench errors, and protects against infinite loops with a timeout.
verilog_toolchain_infoA	Returns active container or host execution runtime info and versions of iverilog, verilator, verible, and sv2v.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zesun33/mcp-verilog'

If you have feedback or need assistance with the MCP directory API, please join our Discord server