DeepSeek Harness Plugin

yxy050208/multisim-mcp#deepseek-harness

Stars ★ 18 Downloads (30d) 1,047 Category Tools & Capabilities Added 2026-08-23 npm multisim-mcp-dsh-plugin

Connects DeepSeek Harness to Multisim MCP for circuit generation, simulation, diagnostics, design optimization, and experiment report export.

Install

# from npm (prebuilt)

dsh plugin --profile web add multisim-mcp-dsh-plugin

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:yxy050208/multisim-mcp#path:/integrations/deepseek-harness

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

This plugin publishes its README in Chinese only.

The npm bundle is multisim-mcp-dsh-plugin@1.3.0-rc.3. The public Python candidate remains multisim-mcp==1.3.0rc1; the source tree also contains the newer 1.3.0rc3 core. This adapter uses the configured Python MCP server; it does not bundle Python or Multisim. New capabilities remain limited to the documented validated circuit families.

Multisim MCP 的 DeepSeek Harness 插件

这是一个可独立安装的 Harness bundle。它把 Multisim MCP 注册为 mcp__multisim__* 工具,并默认使用 experiment Tool Profile。

安装

先在 32 位 Python 中安装与 bundle 同版本的 multisim-mcp,设置该解释器路径, 再把固定版本的 bundle 加入 Harness profile:

$env:MULTISIM_MCP_PYTHON = "C:\path\to\python32\python.exe"
& $env:MULTISIM_MCP_PYTHON -m pip install "multisim-mcp==1.3.0rc1"
dsh plugin --profile web add "multisim-mcp-dsh-plugin@1.3.0-rc.3"
dsh --profile web --dump-config

安装或升级 bundle 后应重新启动该 profile。发布前验证当前源码时,应先用 npm pack .\integrations\deepseek-harness --ignore-scripts 生成 .tgz,再把该 tarball 的绝对路径交给 dsh plugin ... add,以验证与最终发布相同的包边界。

维护者发布前必须运行 Registry 与包边界守卫。首次发布需要本地 2FA;后续版本使用 OIDC 暂存并由维护者 2FA 审批。完整步骤见 docs/DEEPSEEK_HARNESS_NPM_RELEASE.md。

可选环境变量:

  • MULTISIM_MCP_TOOL_PROFILE:core、experiment、optimization 或 full; experiment profile 还包含 build_behavioral_reference 和 run_behavioral_reference,用于明确的 DFF 行为级 ngspice 参考实验; 使用 optimize_design、global_optimize_design、autonomous_correct_design、 submit_global_optimization、submit_autonomous_correction 或 compare_design_variants 时选择 optimization(或 full); evaluate_design_patch 在 experiment、optimization 和 full 中可用; diagnose_design 在四种 profile 中均可用;
  • MULTISIM_MCP_TEMPLATE_DIR:本地组件模板包;
  • MULTISIM_MCP_WORKDIR:实验工作目录;
  • MULTISIM_MCP_ARTIFACT_EXPORT_DIR:允许导出产物的根目录。
  • 自然语言工程工具包括 RC、RLC 和 OPAMP 的 plan/run 入口;后台运行使用 submit_natural_engineering_job,kind 为 rc、rlc 或 opamp。
  • 后台任务通过 get_experiment_job 和 multisim://jobs/{job_id} 查询阶段、取消和证据。
  • 未验证元件模型和未通过拓扑/数值验收的任务会失败关闭,不会仅因生成 .ms14 就报告成功。
  • MULTISIM_MCP_MODEL_ROOT:compile_executable_netlist 重新哈希获批外部模型时唯一允许 读取的本地根目录;模型 URI 必须是该目录内的相对路径。

experiment profile 现在包含 compile_executable_netlist 和 approve_executable_netlist。它们目前只对 signal-passive 生成并确认内存中的引脚级 CircuitDesign / SPICE 预览,其他方案失败关闭;批准凭证只开放成图准备,不会写文件、 添加激励、执行分析或启动仿真。要消费审批凭证,调用 create_schematic_from_netlist 时同时传入完整预览 executable_netlist、审批凭证 netlist_approval 和预览中原样的 spice_netlist;工具会在写入 .ms14 前重新校验绑定, 拒绝缺凭证或被修改的网表,且不会启动仿真。 随后调用 approve_simulation_plan,把同一网表审批绑定到经过安全校验的 ExperimentSpec(分析命令、测量和验收限制);执行时将三份凭证传给 run_verified_circuit_experiment,它会在成图和仿真前再次验证绑定。

不要把 DEEPSEEK_API_KEY 放入 MCP 子进程配置。该凭据只属于 Harness。 MCP 服务器命令在 agent 沙箱之外执行,应当只安装可信发布物并固定版本。

English summary

This package is an installable DeepSeek Harness bundle for Multisim MCP. Install it with dsh plugin --profile web add multisim-mcp-dsh-plugin@1.3.0-rc.3, set MULTISIM_MCP_PYTHON to the 32-bit Python interpreter containing the compatible multisim-mcp release, and restart the profile. Model credentials remain in Harness and are never forwarded to the MCP child process. Maintainer release instructions are in docs/DEEPSEEK_HARNESS_NPM_RELEASE.md.

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.