Skip to main content
Glama

pango-mcp

English · 简体中文

An MCP stdio server that gives any MCP-capable agent — Claude Code, Codex CLI, or your own client — hands-on control of a real FPGA toolchain: simulate, assert, synthesize, scan the JTAG chain, capture on-chip waveforms, and configure real silicon behind explicit confirmation gates.

On the name. The server is pango-mcp because Pango Design Suite is the toolchain it drives end to end — synthesis, place & route, bitstream, ILA, device configuration. Its MCP tools keep the fpga_* prefix: several of them (fpga_sim, fpga_msim_*) drive Icarus Verilog and ModelSim/Questa, which have nothing to do with Pango, and naming those pango_* would be a lie.

Who it's for

You already have an FPGA toolchain installed, and you want an agent to drive it — and to be provably wrong when it is wrong.

That second half is the point. PDS and ModelSim both exit 0 on failure. Every tool here decides success by parsing the log (E: lines, Errors: N, the bitstream success line, UVM error counts), never by exit code, and returns a structured verdict — ok, parsed errors, timing/utilization, diagnostics — instead of a raw log the model can narrate its way around.

Related MCP server: vivado-mcp-agent

What works with what

Capability

Backend

You need

Verilog simulation, assertions, waveforms

Icarus Verilog

iverilog on PATH

VHDL, coverage, UVM, encrypted IP

ModelSim / Questa

install + license

Synthesis, P&R, bitstream, reports

Pango Design Suite

install + license

JTAG scan, SRAM/SPI configuration

PDS cdt_js, or bare-metal FT2232

board + cable

On-chip debug (ILA/FLA capture)

PDS fabric inserter + JTAG

board + cable

Primitive / IP / doc retrieval

offline corpus

built from your PDS install

Platform. The server runs on any OS with Node ≥18.17 — it starts cleanly with nothing installed and reports what is missing. The vendor tools it drives are Windows-first in practice, and the bare-metal JTAG path (fpga_jtag_*, fpga_ila_*) is Windows-only (it loads ftd2xx.dll through ctypes.WinDLL). Python 3 is required for the JTAG layer only.

Install

git clone https://github.com/Renkos1/pango-mcp.git
cd pango-mcp
pnpm install
pnpm check          # syntax gate over every module
pnpm test:unit      # 33 tests — no toolchain, no board needed

Then point it at your tools. Copy pango-mcp.env.example to a file outside the install directory, fill in your paths, and set PANGO_MCP_ENV_FILE:

PANGO_MCP_PDS_2025=<path>\bin\pds_shell.exe
PANGO_LICENSE_FILE=<path>\pango.lic
PANGO_MCP_MODELSIM_HOME=<modelsim install root>
PANGO_MCP_MODELSIM_LICENSE=<path>\modelsim.lic

The server is spawned over stdio with a safe env subset, so it does not inherit your shell's LM_LICENSE_FILE/MGLS_LICENSE_FILE. Setting PANGO_MCP_MODELSIM_LICENSE is required for real fpga_msim_* runs.

Nothing is baked in: every path comes from config or env, and an unset one fails with a message naming the knob. pango-mcp.config.json is an alternative to env vars and additionally declares remote hosts and board profiles — see pango-mcp.config.example.json.

Register with an agent

Claude Code:

claude mcp add pango -- node <ABSOLUTE_PATH_TO_REPO>/src/index.mjs

Codex CLI (~/.codex/config.toml):

[mcp_servers.pango]
command = "node"
args = ["<ABSOLUTE_PATH_TO_REPO>/src/index.mjs"]

Project-level .mcp.json:

{ "mcpServers": { "pango": { "command": "node", "args": ["<ABSOLUTE_PATH_TO_REPO>/src/index.mjs"] } } }

Try it

  1. Ask the agent to call fpga_env — you should see your iverilog/PDS/ModelSim paths.

  2. Have it write a small design + testbench, then call fpga_sim with wave:true.

  3. Have it call fpga_assert on the result (log_contains: PASS, vcd_final_eq: q == 10).

  4. Negative control: ask for a testbench that $fatals. ok must come back false. If it doesn't, that is the bug worth reporting.

Tools

43 tools, tiered. Call fpga_capabilities for the live catalog — it is the authoritative list, generated from the same source the tests check.

The six you will actually use:

Tool

Does

fpga_env

What toolchains this machine has, with paths

fpga_sim

iverilog compile + run; optional VCD and one-step waveform

fpga_assert

Declarative pass/fail over a log or VCD — the real verdict

fpga_wave

Any VCD → SVG/HTML timing diagram, optionally opened in a browser

fpga_pds_compile

PDS through gen_bit_stream, with parsed errors and timing

fpga_pds_scan

Read JTAG IDCODEs — read-only, always safe

Everything else groups into: ModelSim (fpga_msim_*), PDS build/report (fpga_pds_*, fpga_log_extract), device and flash (fpga_flash_*, fpga_gen_*, fpga_cdt, fpga_exe), bare-metal JTAG (fpga_jtag_*), on-chip debug (fpga_ila_*), and retrieval (fpga_primitive_lookup, fpga_ip_lookup, fpga_doc_search, fpga_vault).

Full reference, including every argument: README.zh-CN.md.

Safety

This server is not a sandbox. It runs vendor binaries and writes to real silicon with your privileges. Run it as a local subprocess of a trusted agent; do not expose it to untrusted callers. Read SECURITY.md before wiring it into anything shared.

Every tool that writes to a device stops at a confirmation gate: it requires confirm:true, a matching expectIdcode, and a real prior scan before it does anything. Without confirmation it returns phase:"confirm" and touches nothing. This is enforced in code and covered by tests, not just documented.

SPI flash programming is persistent and can leave a board unable to boot from flash. SRAM configuration is volatile and recoverable.

Cost control

Returns are compact by default — errors, timing, utilization, diagnostics, key lines — with the full log written to disk and reachable via detail:"full". Builds are cached by a hash of source content plus project semantics, so an unchanged source returns the previous summary instantly. Knowledge retrieval is keyword-scored with no embedding model and no API call; semantic search is opt-in and falls back silently to keyword when unconfigured.

Docs

  • CONTRIBUTING.md — three contribution tiers; most of this is testable with no hardware

  • SECURITY.md — threat model, what's in scope, operator guidance

  • test/README.md — what every test needs and what it does without it

  • CHANGELOG.md — including the pre-1.0 stability policy

  • docs/ILA-FINDINGS.md — how the headless FLA capture path was derived

  • skills/ — the Pango PDS flow skill shipped with the server

License

Apache-2.0. See NOTICE for vendor trademarks and the exact provenance of the shipped knowledge corpora — this project bundles no vendor software and no vendor documentation text.

Available Tools

45 tools
fpga_assert仿真断言判定A

对 fpga_sim 日志和/或 VCD 做声明式断言判定。支持日志包含/正则与 VCD 终值/指定时刻/永不等于。

Inputs: assertions (required), log, vcdPath, knowledge.

fpga_capabilities能力目录 (分层)A

返回分层工具目录(tier0 热点/tier1 常用/tier2 专家) + 长尾能力如何经 fpga_cdt/fpga_exe 触达 + 成本/安全注意。用于发现完整 PDS 控制面而不撑大每个工具 schema。也回 serverVersion(运行实例的代码指纹)——与工作树 HEAD 不一致即服务陈旧,需重启。

Inputs: no named parameters.

fpga_cdtCDT 通用 Tcl 直通 (受护栏)A

对 cdt_js 跑任意 cfg_*(cdt_cfg) 或 dbg_*(cdt_dbg) Tcl,覆盖扫链/读属性/配置/SPI flash/ILA 抓波/virtual-IO 全套。读类(scan/read/list/help)自由;写器件类(cfg_program/cfg_jtag_flash_erase|program/dbg_program 等)需 confirm:true + expectIdcode(先 scan 校验匹配)。connect:true(默认)自动包 connect/scan_chain/disconnect,只需给 commands;raw tcl 用 {{PORT}} 占位端口。

Inputs: tcl, host, port, detail, +8 more.

fpga_envFPGA 环境探测A

报告 FPGA 工作流可用工具:iverilog/vvp、verilator、gcc、node/pnpm,以及 PDS/cdt 路径、本地 PDS license 可用性/配置来源和本机 MCP server 实例归属。默认探本机;传 host 则经 SSH 探该远程执行设备(execution-device layer,与本机同一套探测逻辑)。

Inputs: host.

fpga_exePDS bin 工具直通 (受护栏)A

在 PDS bin 目录跑构建/分析类工具(ip_generate/ip_compiler/ip_tar/cdt_bts/ppc/ppp/rf_analyzer/evp/pne/state/de/pce/ta)并回提取后的输出。任意 bin exe 都可用 -help/-version 探测其用法。器件/JTAG 类(cdt_cfg/cdt_dbg/cdt_js/cdt_ins)与 GUI(pds.exe/assistant) 不在此列——用 fpga_cdt / fpga_pds_run。

Inputs: exe (required), cwd, args, host, +3 more.

fpga_flash_spi烧录板载 SPI FlashA

通过 FPGA JTAG->SPI bridge 持久烧录。危险动作:必须 confirm=true,且内部先 scan 并校验 expectIdcode。

Inputs: sbit (required), flashPart (required), expectIdcode (required), host, +6 more.

fpga_flash_sram烧录 FPGA SRAMA

烧 .sbit 到 FPGA SRAM。危险动作:必须 confirm=true,且内部先 scan 并校验 expectIdcode。

Inputs: sbit (required), expectIdcode (required), host, port, +4 more.

fpga_gen_chain_file生成 SPI 链式文件 (cfg_gen_chain_file)A

离线把两个或更多 .sbit 合成 SPI chain 文件。不连器件。可选生成 bin 及字节/位反转,全部参数化。

Inputs: infile (required), outfile, pdsVersion, timeoutSec, +3 more.

fpga_gen_multi_file生成多启动数据流 (cfg_gen_multi_file)A

离线把两个或更多 .sbit 合成多启动/升级数据流(黄金+应用回退、SPI/BPI 升级等)。不连器件。infile 与 sbitStartAddress 由调用方给定,偏移不写死;type 选数据流类型。

Inputs: type (required), infile (required), outfile, pdsVersion, +4 more.

fpga_gen_sfc生成 SPI Flash 镜像 (.sfc)A

离线把 .sbit 转成 .sfc(cfg_gen_sfc),不连器件、不需 cable/confirm。flash 型号(-device_name)、读 opcode、起始地址全部参数化,可烧任意所连 FPGA 的配置 flash;不内置任何板级默认。多启动用 fpga_gen_multi_file。

Inputs: sbit (required), sfc, isX8, opcode, +9 more.

fpga_ila_adc_readILA: 读片上 ADC 寄存器(温度/电压等)A

便捷封装:经 GUI Tcl Console 执行 dbg_adc_read_reg -address <addr> 读片上 ADC 寄存器(如 die 温度),回读并解析数值。底层同 fpga_ila_console(session-1 UIAutomation 驱动,cable 由 GUI 打开)。

Inputs: address (required), host, user, timeoutSec.

fpga_ila_buildILA: 仪表化构建(生成 .fic→注册→gen_bit_stream)→ sbit + 构建报告网页A

把 ILA 仪表化构建合并成一次自纠调用:旁路综合→Fabric Inserter ins_list_nets 权威解析→FIC 前精确成员校验→生成/注册 .fic→gen_bit_stream。多实例同名回 ambiguous,未被 Inserter 验证或已优化的信号都会在修改工程前 fail-fast。返回 sbit+fic+报告;本地默认把 sbit 交给 fpga_jtag_flash,再把 fic 交给 fpga_jtag_capture。GUI flow 仅作远程/特殊功能 fallback。

Inputs: pdsPath (required), signals (required), host, ficPath, +5 more.

fpga_ila_captureILA GUI fallback: 抓波→导出→交互波形查看器A

GUI fallback,不是本地默认抓波路径;本地普通 FLA 优先 fpga_jtag_capture。仅在裸机 capture 不支持所需功能或远程 GUI 场景下,基于已完成的 fpga_ila_open 跑 dbg_fla_* 序列、导出 VCD、解析分组并生成交互波形查看器。

Inputs: fla, host, user, clock, +6 more.

fpga_ila_consoleILA: 在 Fabric Debugger 的 Tcl Console 里执行 tcl(AI 调试控制台)A

无头 cdt_dbg 开不了 cable(open_cable 死锁,见 docs/ILA-FINDINGS.md);改为驱动 GUI Fabric Debugger 自带的 Tcl Console——它跑同一个 tcl 引擎且 cable 已由 GUI 打开。本工具在 GUI 所在的交互桌面(session 1)用 UIAutomation 把 tcl 打进 Console 并回读 transcript 增量,纯 AI 驱动、零人工点按。本机/远程皆可:本机(MCP 即跑在用户 session 1)直驱,远程经 SSH host 跳 session 1。可跑任意 dbg_* 命令(读 IDCODE/ADC、抓波 dbg_fla_*、import fic、program 等)。前提:目标桌面上 Fabric Debugger GUI 已打开并连好工程。写器件类命令(dbg_program 等)需 confirm:true + expectIdcode;工具先经同一 Console 只读 dbg_read_device_id 并匹配。

Inputs: tcl (required), host, user, confirm, +2 more.

fpga_ila_flowILA GUI fallback: 一键烧录→调试器→抓波A

GUI fallback:仅当裸机 fpga_jtag_flash→fpga_jtag_capture 不支持目标功能,或必须使用远程交互桌面时采用。危险动作必须 confirm:true。流程:可选推送工程→释放 cable→scan+IDCODE→烧录→fpga_ila_open→fpga_ila_capture→teardown;逐 stage 回报。普通本地 FLA 抓波不要优先走本流程。

Inputs: sbit (required), projectDir (required), expectIdcode (required), fla, +16 more.

fpga_ila_generate_ficILA: 生成 .fic 配置(纯本地代码生成,低层原语)A

低层原语:把器件 + 时钟网 + 信号网名清单写成符合 Pango .fic 规范的文本。入参必须是综合后真实网名——flatten 会改名(寄存器 tx→nt_led[0]、时钟 clk→nt_clk),勿假设 RTL 名保留;不知真名先用 fpga_ila_list_nets,或直接用 fpga_ila_build(接受期望名并自动解析)。生成后用 fpga_pds_register_fic 注册→fpga_pds_run gen_bit_stream 出仪表化 sbit。

Inputs: part (required), ficPath (required), signals (required), clockNet (required), +3 more.

fpga_ila_list_netsILA: 发现可抽头的真实网名(综合→解析网表)A

解决 ILA 抽头的根本问题:综合 flatten 后的网名 ≠ RTL 名。本工具在隔离旁路副本中 compile→run_ads,再调用 Fabric Inserter 的 ins_list_nets 取得 .fic 真正可消费的全层级标量网名;不会从模块定义猜路径。可选 signals 会展开唯一总线并返回 exact/renamed/hierarchical/ambiguous/unverified/pruned,多实例同名必须传完整层级。fpga_ila_build 使用同一权威清单做 FIC 前 fail-fast。

Inputs: pdsPath (required), signals, pdsVersion, timeoutSec.

fpga_ila_openILA GUI fallback: 打开调试器→扫链→检测核A

GUI fallback,不是本地默认路径。本地普通 FLA 抓波优先 fpga_jtag_flash → fpga_jtag_capture;仅当裸机 capture 不支持目标功能,或需要远程交互桌面时使用。本工具把 Fabric Debugger 拉起并就绪:session-1 启动 cdt_dbg → Search JTAG Chain → 处理 Open Cable 弹窗 → 扫描 UIA 树检测 DebugCore。前提:projectDir 是已构建且含 FLA 核的工程目录。

Inputs: projectDir (required), host, user, pdsVersion.

fpga_ip_lookupPDS IP 核查询A

查 PDS IP 目录(~65 核:PLL/RAM/DRM/FIFO/APM/DDR/Debug 等):slug=精确返回该核 header/支持器件/参数(含 enum 选项)/数据手册 PDF 路径;query=关键词召回;category=按类(子串匹配,如 'PLL'/'Memory'/'DDR');都不传=返回核清单汇总。每个核自带 datasheet PDF。

Inputs: mode, slug, limit, query, +2 more.

fpga_jtag_capture本地首选:裸机 JTAG FLA 抓波A

本地 ILA 的默认抓波路径:经 FT2232 武装片上 FLA、读回采样缓冲并导出(VCD/JSON/CSV/可选 raw),不走 cdt_js/GUI。通常先 fpga_jtag_flash,再调用本工具;width/depth/信号名来自设计 .fic 或显式给定。PDS 不在 .fic 暴露物理 stride:reader 先按 vendor 标准 width+1 精确探测,必要时扩大读取并仅凭 protocol padding 稀疏度推断;歧义 fail-closed,也可显式给 paddingBits。capture.framing 始终返回 paddingOneCounts/header/tail/read length。可选值/边沿触发(--trig),需 ila.mjs 建过 Match-Unit 的 FLA;窗口按触发对齐返回。导出路径的 parent 不存在时自动递归创建。

Inputs: csv, fic, raw, vcd, +11 more.

fpga_jtag_flash裸机 JTAG 烧录 SRAM (SVF 回放)A

经 FT2232 回放 CRAM SVF 配置 FPGA(SRAM、易失/可逆,~15s@6MHz),校验 done bit。危险动作:必须 confirm=true,并先裸机 scan 校验 expectIdcode;SVF 内仍做第二次 IDCODE TDO 检查。给 --sbit 时自动离线生成/缓存 SVF。不走 cdt_js/GUI。

Inputs: expectIdcode (required), svf, sbit, tckHz, +5 more.

fpga_jtag_gen_svf离线 .sbit→CRAM .svf (cdt_cfg)A

经 cdt_cfg cfg_one_step_create_svf 把 .sbit 转成 CRAM(SRAM) 配置 SVF。离线、不连 cable,给 fpga_jtag_flash 复用。PDS bin/license 默认从 pango-mcp 配置/环境自动发现。

Inputs: sbit (required), svf, pdsBin, license, +2 more.

fpga_jtag_scan裸机 JTAG 扫描 (MPSSE)A

经 FT2232 直读 IDCODE,不走 cdt_js/PDS、无需 license。只读、设备安全。与 fpga_pds_scan 互斥用 cable:cdt_js 在跑时先停。

Inputs: tckHz, channel, timeoutSec.

fpga_log_extract日志关键信息提取A

对一段日志(或日志文件)按 profile 抽取关键信息:pds(错误码/阶段/时序/资源/已知问题)、cdt(IDCODE/done bit/verify)、sim(失败标记)。用于对落盘日志二次廉价提取,省 token。

Inputs: log, logPath, profile.

fpga_msim_compileModelSim 仅编译 (vlog/vcom)A

只编译(不运行 vsim):Verilog/SV→vlog、VHDL→vcom,做语法/早期检查。加密 IP(.vp/.svp,IEEE-1735)由 vlog 原生解密。ok 由 'Errors: N' 与 ** Error 判定,不信退出码。紧凑摘要 + detail:'full' + 缓存。

Inputs: workdir (required), lib, host, cache, +7 more.

fpga_msim_doModelSim 通用 do 脚本直通 (vsim -c)A

对 vsim -c 跑任意 do/Tcl,覆盖长尾:coverage(coverage save/report)、force/examine、add wave、UVM(+UVM_TESTNAME)、WLF 分析、自定义 run 控制等。强制 headless(-c)+末尾自动 quit -f(防挂)。纯仿真脚本自由跑;含可触达宿主的命令(Tcl exec / file delete|rename|copy|mkdir / open 写)需 confirm:true(仿 fpga_cdt 写器件护栏)。可给 top 让工具 vsim .,或在脚本内自行 vsim/vlog/vcom。

Inputs: workdir (required), lib, top, host, +6 more.

fpga_msim_exeModelSim bin 工具直通 (受护栏)A

在 ModelSim bin 目录跑库/覆盖率/波形/工具类 exe(vlib/vmap/vdir/vcover/wlf2vcd/vcd2wlf/vgencomp/vmake/vopt/sccom)并回提取后的输出。任意 bin exe 都可用 -help/-version 探测。编译/仿真(vlog/vcom/vsim)有专用工具(fpga_msim_compile/sim/do),不在此列。

Inputs: exe (required), cwd, args, host, +2 more.

fpga_msim_simModelSim 仿真 (vlib+vlog/vcom+vsim -c)A

用 ModelSim 头less 编译(Verilog/SV→vlog,VHDL→vcom)并运行(vsim -c -do)一个设计(含 testbench)。不信退出码:以 transcript 的 ** Error/Fatal 与 'Errors: N' 判定 ok($fatal 时 vsim 仍退 0)。可出 VCD 供 fpga_assert 判定;可选 coverage 返回结构化覆盖率(分支/语句/条件/翻转 %)。默认紧凑摘要 + detail:'full' + 按输入 hash 缓存。VHDL 是相对 fpga_sim(iverilog) 的增量能力。

Inputs: top (required), workdir (required), lib, uvm, +20 more.

fpga_msim_view打开 ModelSim 波形 GUI (本机交互查看)A

在本机打开 ModelSim 图形界面查看波形(交互式缩放/测量/层级展开)——给用户做深度查看的渠道。输入 VCD(自动 vcd2wlf 转 WLF)或 WLF;signals 可预选 add wave,省略则 add wave -r /*。GUI 进程脱离 MCP 独立运行(detached),工具立即返回。注:开的是本机 GUI(远程仿真的 VCD 已拉回本地,直接对本地路径用此工具);要静态图像/弹浏览器用 fpga_wave。launch:false 只做转换+给出命令不真正弹窗。

Inputs: radix, groups, launch, signals, +3 more.

fpga_pds_batchPDS 独立工程变体批量运行(最多 2-way)A

并行运行多个已准备好的独立 PDS project clone,并汇总每个 variant 的 timing/errors/artifacts。安全门:每个 pdsPath 必须位于唯一且互不嵌套的项目目录,prj_work_dir/prj_impl_dir 不得外置;同一 .pds 或共享 prj_tasks 会在启动前拒绝。默认且最高 2-way(P&R 内存密集)。任一 variant 失败则顶层 ok=false,但保留全部逐项结果。

Inputs: variants (required), cache, runTarget, pdsVersion, +3 more.

fpga_pds_compilePDS Headless 构建 (gen_bit_stream 预设)A

fpga_pds_run 的出比特流预设:默认 runTarget=gen_bit_stream,跑全流程产 .sbit。其余行为同 fpga_pds_run(紧凑摘要 + detail/cache + effsoftecrypt 自检)。

Inputs: pdsPath (required), host, cache, detail, +4 more.

fpga_pds_create_project创建最小 PDS 工程A

创建一个可供 pds_shell 尝试编译的最小 .pds 工程(RTL/约束/.pds)。器件无关:目标 family/device/speedgrade/package 是板级物理信息,由用户/Target Profile 给定,工具不内置默认/不猜。推荐传 board:(config 的 boards 里一套完整 target,含引脚→自动生成 FDC);或把 4 个字段全显式给。缺则报错点名所缺。

Inputs: projectDir (required), top, name, board, +6 more.

fpga_pds_register_ficILA: 把 .fic 注册到 .pds(Fabric-Inserter widget)A

把已生成的 .fic 写入 .pds 工程的 Fabric-Inserter widget(<action name='fic'>/wgt_my_fic_src),让接下来的 fpga_pds_run gen_bit_stream 走 inserter→生成 instrumented bitstream。自动备份原 .pds 为 .bak_;支持 PDS 2025.2 的 XML 形态与早期 sexpr 形态。

Inputs: ficPath (required), pdsPath (required).

fpga_pds_reportsPDS 报告解析A

解析 PDS 构建日志、时序、资源与 bitstream 输出;不运行 PDS。

Inputs: log, top, logPath, pdsPath, +1 more.

fpga_pds_runPDS Headless 运行 (任意 -run 目标)A

用 pds_shell.exe -project <x.pds> -run 运行任意流程阶段。target ∈ {compile, synthesize, dev_map, pnr, report_timing, report_power, gen_bit_stream, gen_netlist}(注意 dev_map/pnr,非 device_map/place_route;早期目标如 dev_map 可快速拿资源不跑 P&R)。不信退出码,解析 E:/bitstream success line + effsoftecrypt 自检。默认紧凑摘要 + detail:'full' 兜底 + 按输入 hash 缓存。

Inputs: pdsPath (required), runTarget (required), host, cache, +4 more.

fpga_pds_scanPDS JTAG 扫链A

启动/复用 cdt_js,并用 cdt_cfg 扫 JTAG 链、读取 IDCODE。只读动作。默认本机;传 host 则在该远程设备上扫(execution-device layer)。

Inputs: host, port, maxDevices, pdsVersion, +3 more.

fpga_primitive_lookupLogos2 原语查询A

查 Logos2 原语库(gtp_lib.v, 153 个 GTP_* 原语):name=精确查端口/参数/最小例化模板;category=列某类(clock_pll/ff_latch/lut/mem/io_buffer/serdes_ddr/mipi/pcie/analog/config_misc);query=关键词召回;都不传=返回分类汇总。结构化、省 token。

Inputs: mode, name, limit, query, +1 more.

fpga_project_infoPDS 工程信息解析B

解析 .pds 工程文件,返回目标器件、顶层源文件、源文件列表、约束文件与括号平衡检查。

Inputs: pdsPath (required).

fpga_server_cleanupMCP server 实例审计与孤儿清理A

审计本机 pango-mcp stdio server 的 PID、父进程、年龄与私有内存;只把父进程已消失或父 PID 已复用的实例列为 orphan_candidate。默认只读;confirm:true 才终止经二次身份复核的孤儿。仍由客户端持有的实例永不跨任务强杀。

Inputs: pids, confirm, minAgeSec.

fpga_simVerilog 仿真 (iverilog+vvp)A

用 iverilog 编译 + vvp 运行一个 Verilog/SystemVerilog 设计(含 testbench),返回日志与 ok 判定;可选注入 wrapper 生成 VCD。

Inputs: top (required), workdir (required), vcd, wave, +6 more.

fpga_vault验证资产知识库A

检索/读取/校验 knowledge-vault,并在资产被读取时写 trace asset_use;recall 只读扫描 trace 反查受影响会话,不自动改 tier/status。candidate 只由 fpga_assert 或 fpga_ila_flow 的客观绿结果写入。

Inputs: action (required), id, tier, limit, +6 more.

fpga_wave仿真波形绘图 (VCD→SVG/HTML 图像)A

把 VCD(任意来源:fpga_sim/iverilog 或 fpga_msim_sim/ModelSim 的 artifacts.vcd)渲染成数字时序图。产出 .wave.svg + .wave.html 文件并返回路径;inlineSvg(默认 true)在结果里带完整 SVG 供能渲染的 AI 直接展示;open:true 用默认浏览器把波形弹给用户看。signals 选信号、maxSignals 控规模(默认 40)。需要交互式深查/缩放用 fpga_msim_view 打开 ModelSim GUI。

Inputs: vcdPath (required), open, width, signals, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 45 tools

    Disambiguation2/5

    Many tools overlap in purpose or responsibility: there are three ILA capture paths (fpga_jtag_capture, fpga_ila_capture, fpga_ila_console), two scan tools with different stacks (fpga_pds_scan, fpga_jtag_scan), and multiple ways to build/compile (fpga_pds_run, fpga_pds_compile, fpga_pds_batch, fpga_ila_build). The descriptions are long and detailed, but an agent would struggle to confidently choose between them without deep context.

    Naming Consistency4/5

    The fpga_ prefix and snake_case verb_noun pattern are consistent (fpga_pds_run, fpga_flash_sram, fpga_ila_open), with occasional deviation (fpga_pds_create_blink_project, fpga_vault, fpga_env). Minor irregularity in domain grouping (some tools use fpga_pds_, some fpga_ila_, some fpga_jtag_, some no subdomain) but overall readable and predictable.

    Tool Count1/5

    45 tools is far beyond the well-scoped range, and many are thin wrappers (fpga_ila_adc_read, fpga_msim_compile, fpga_msim_do, fpga_pds_compile) around more general tools, resulting in a heavy, sprawling surface that will tax context and selection.

    Completeness5/5

    The covered domain—Pango FPGA build, JTAG scan/flash, ILA capture, simulation, and IP/documentation lookup—is remarkably complete, with multiple fallback paths and long-tail escape hatches (fpga_cdt, fpga_exe, fpga_msim_do). There are no obvious dead ends; if anything the surface is over-complete.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with a complete FPGA toolchain for HDL linting, simulation, synthesis, and place-and-route across various hardware targets. It features a GitHub-backed IP core registry that enables users to search for and import MIT-licensed cores directly through their chat interface.
      15
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for deterministic Vivado FPGA automation including project scaffolding, simulation, synthesis, implementation, and gated bitstream generation.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for FPGA toolchain operations including linting, simulation, synthesis, place-and-route, bitstream programming, and IP core registry via GitHub.
      25
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lean MCP server that lets AI agents drive Xilinx Vivado for synthesis, implementation, simulation, and diagnostics through 30 curated tools and raw Tcl execution.
      Apache 2.0