A MCP server that wraps Redwood EDA’s SandPiper-SaaS compile function to convert TL‑Verilog (TLV) files into SystemVerilog/Verilog. Exposes every SandPiper flag as its own MCP tool parameter for introspection and easy automation. In other words, tell in natural language(English) what you want the compiler to do. Refer prompt for prompt examples.
This project uses UV to manage its virtual environment and dependencies.
If you don’t already have the UV CLI installed, you can install it using just pip
(no pipx
required):
pip install --user uv
Or, if you prefer an isolated install via pipx
:
pipx install uv
Verify that it’s on your PATH:
uv --version
Clone this repo
git clone https://github.com/shariethernet/mcp-sandpipersaas.git
From the project root, run:
uv install
This will create (or reuse) a .venv/
directory and install all required packages.
The easiest way to start the MCP server is via the uv
command (part of the UV toolkit):
uv --directory <path_to_this_repo>/mcp-sandpiperasaas run mcp-sandpiperasaas.py
This will launch the MCP server over stdio, ready to accept tools/list
and tools/invoke
requests.
If you prefer the lightweight uvx
bundle:
uvx run mcp-sandpiperasaas.py
It will detect and run the MCP server in the current directory.
You can configure your MCP-server with the following json for Cline or Claude Desktop or any MCP Client that atleast supports mcp tool calling: (Note for paths in windows use \\
instead of /
)
{
"mcp-sandpiperasaas": {
"command": "uv",
"args": [
"--directory",
"<path to this repo>/mcp-sandpiperasaas",
"run",
"mcp-sandpiperasaas.py"
],
"autoApprove": [
"sandpiper_compile"
]
}
}
command
: the CLI you use (uv
oruvx
)args
: arguments to point at the project folder and mcp scriptautoApprove
: list of tool names that can run without extra confirmation (“sandpiper_compile”)