BlockWerk

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as tech.blockwerk/mcp and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 5 Oct 2026. Not supplied by the maker.

• describe_canvas

  Returns a structured description of all blocks and connections currently on the canvas. Set "compact" to true for a token-efficient summary.

• get_available_blocks

  Returns the block types in the library with their descriptions, configurable parameters, and exact input/output port IDs. Without a filter it returns a compact list of all types; with a list of type I

• add_block

  Add a new block to the canvas. Returns the new block ID.

• connect_blocks

  Connect an output port of one block to an input port of another. Automatically resolves common port aliases (e.g., "in" -> "signal" for uPlotDisplay, "in" -> "error" for PIDController, "+" / "-" for S

• update_params

  Update one or more parameters of an existing block.

• delete_block

  Delete a block and all its connections from the canvas. This is a destructive action that asks the user for approval in the BlockWerk tab.

• load_diagram

  Atomically replaces the entire canvas with a complete diagram defined as a BlockWerk project JSON string. The JSON has a "blocks" array (each block needs a unique "id" and "type"; "x"/"y"/"params" are

• export_diagram

  Exports the current canvas project as a complete BlockWerk JSON string.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.