chiplab

Chiplab gives AI coding agents direct access to chip-accurate firmware simulation — no physical hardware required. Connect your agent once, then just describe what you want in plain language ("test this firmware on an STM32"), and Chiplab handles the rest: building, uploading, running on a virtual board, and reporting back the results.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

模型生成摘要（rules/v1 · 2026-09-27 16:11）：Chiplab gives AI coding agents direct access to chip-accurate firmware simulation — no physical hardware required
这是模型对公开材料的总结，不是官方声明，请以原链内容为准。

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://chiplab--veecle.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "chiplab": {
      "url": "https://chiplab--veecle.run.tools"
    }
  }
}

能力清单

工具	说明
ask	Query the Chiplab knowledge base with a natural language question. This can be used to get help about what Chiplab is, how to use it etc. For a general overview, read `/mcp/resources/docs/overview.md` directly instead of calling this tool. URLs containing `/mcp/resources/` in responses correspond to MCP resources on this server, if you have MCP resource tools use them, otherwise use a normal web fetch.
cancel_task	Cancel a currently running task
get_task_info	Check the current lifecycle status of the task
get_task_result	Get the task's result, blocking if not yet ready
issue_download_ticket	Issue a time-limited, presigned URL to download an artifact produced by a firmware simulation run without further authentication. This tool requires a `run_id` previously obtained from the `run` tool and an `artifact_name` as listed by the `list_run_artifacts` tool. The returned `download_url` accepts a raw `GET` request and responds with the artifact bytes as the body (e.g. `curl DOWNLOAD_URL`).
issue_upload_ticket	Issue a time-limited, presigned URL to upload an artifact without further authentication. The returned `upload_url` accepts a raw `PUT` request with the artifact bytes as the body (e.g. `curl --upload-file firmware.elf UPLOAD_URL`). The `artifact_id` field is the identifier to pass to tools consuming uploaded artifacts once the upload has completed.
list_run_artifacts	List every artifact produced by a firmware simulation run. This tool requires a `run_id` previously obtained from the `run` tool. The response lists the location of each artifact the run generated. To read the content of a listed artifact, pass its name to the `issue_download_ticket` tool.
run	Run a new firmware simulation on the given board. This tool requires an `artifact_id` previously obtained from the `issue_upload_ticket` tool. The response from that tool also includes the URL the artifact must be uploaded to before this tool is called. Use the Ask tool for further details about uploading artifacts. Once the triggered task responds with OK, the response contains the list of output artifacts generated by the run. This list may be empty if the run produced no output artifacts. You can query the same list again at any time using the `list_run_artifacts` tool with the corresponding `run_id`.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。