FpgaZeroMCP logo

FpgaZeroMCP

Unclaimed

by lcapossio

An open-source Model Context Protocol server that gives AI assistants a complete FPGA toolchain — lint, simulate, synthesize, place-and-route, and a live IP core registry backed by GitHub.

Install

$python /path/to/fpgaZeroMCP/server.py

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
fpgaiplintmcpverilogvhdlvhdl-code

More in AI & ML

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

26 of 26 tools

Documented tools (26)

From project documentation. A server handshake does not verify each tool’s description or behavior.

build_status

Check progress — status, elapsed time, parsed phase/utilization/timing

cancel_build

Kill a running background build

check_tools

Report which OSS CAD Suite tools are installed, with paths and versions

cleanup_build_logs

Delete old build logs by age and total size

format_hdl

Auto-format via verible-verilog-format (V/SV) or vsg (VHDL)

generate_ip

Get a parameterized instantiation snippet + source files

get_diagnostics

Structured per-line diagnostics — Verilator → verible fallback (V/SV), GHDL (VHDL)

get_ip_core

Fetch manifest and HDL source for a core

import_fusesoc_core

Import a local FuseSoC CAPI2 .core file

import_github_core

Download a GitHub repo into the local registry

lint_hdl

Syntax/error check via iverilog (V/SV) or GHDL (VHDL) — single file

lint_project

Lint multiple files together so cross-module references resolve

list_boards

Enumerate built-in board presets (target/device/package/clock)

list_builds

List all tracked builds (running and finished)

list_ip_cores

Browse the local registry, filter by category

LiteX

litex_build

Run a LiteX board target with --build

litex_flow

Run a LiteX board target with fully custom args

litex_soc

Generate a LiteX SoC without building gateware

place_and_route

Yosys + nextpnr in one step. Board presets, constraint auto-detection, bitstream written to disk (bitstreampath)

program_fpga

Flash a bitstream via iceprog or openFPGALoader

reload_registry

Re-scan core directories without restarting the server

search_github_cores

Search GitHub for MIT-licensed FPGA IP repos

simulate

Compile and run testbenches — iverilog (V/SV) or GHDL (VHDL). Accepts code, files, or projectdir. Returns verdict + VCD summary

start_build

Start a long-running command in the background (allowlisted EDA tools only)

synthesize

Yosys synthesis with resource stats. Accepts code, files, or projectdir. Verilog, SV, VHDL

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about FpgaZero MCP Server

How do I connect FpgaZero MCP Server to Claude?
The listing records `python /path/to/fpgaZeroMCP/server.py` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Cursor, Windsurf as compatible clients.
Is FpgaZero MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can FpgaZero MCP Server do?
FpgaZero MCP Server documents 26 tools to the agent, including build_status, cancel_build, check_tools. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.