Servidor MCP de BlockWerk

• Nombre en el registrotech.blockwerk/mcpverificado en el registro MCP

El nombre en el registro está bajo blockwerk.tech. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-24
• Herramientas42
• El servidor se llamablockwerk-mcp
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-24 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 211 ms.

• Sus herramientas hacen todos los casos de uso comprobados: build control system block diagrams in the browser; run block diagram simulations with a WebAssembly engine.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta327 ms
• Espacio en el contexto del agente≈ 5760 tokenslas definiciones de todas sus herramientas (42), que el agente lleva en cada turno
• Definiciones de herramientasA · 98 de 100
• Resultados tipados0 de 42 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 4 de 42

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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 IDs it returns full details for those…

• 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 Subtraction).

• 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 optional) and a "connections" array…

• export_diagram

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

• get_share_link

  Returns a link that opens the current diagram on the BlockWerk canvas. The whole project travels compressed inside the URL, so it needs no account and nothing is uploaded. Opening the link in a browser shows the diagram, where the…

• clear_canvas

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

• tidy_layout

  Automatically rearrange all blocks on the canvas into a clean, left-to-right flow.

• batch_commands

  Executes multiple canvas manipulation and background job commands in a single round-trip. Use "handle" strings to refer to blocks added earlier in the same batch. When adding TextNote annotations, set "anchors" to the handles/IDs of the…

• analyze_topology

  Analyzes the block diagram structure: detects feedback loops, signal paths, and system order.

• get_signal_data

  Returns time series data from a Scope block output for analysis.

• calculate_metrics

  Calculates step response metrics from signal data: rise time, settling time, overshoot percentage, and steady-state error.

• get_analysis_measurements

  Retrieves the currently active pinned measurements and their computed values across plotted signals in the Analysis panel.

• evaluate_spec_mask

  Evaluates signal data against automated design specifications and tolerance corridors (rise time, settling time, overshoot %, steady-state error, min/max limits).

• get_architect_memory

  Returns the persistent memory object of the Architect.

• update_architect_memory

  Updates the persistent memory of the Architect. Provide a JSON object with keys to update/merge.

• validate_engineering_units

  Checks the consistency of engineering units across the diagram. Detects incompatible connections and missing units.

• validate_canvas

  Performs pre-flight topological and numerical integrity checks on the canvas. Detects unconnected required input ports, isolated blocks, parameter domain anomalies, and direct algebraic feedthrough loops.

• get_canvas_preview

  Captures a visual screenshot preview of the canvas branded with the official BlockWerk watermark badge and returns the live interactive URL to view and edit the diagram online.

• get_templates

  Lists the built-in, verified BlockWerk diagrams: classic control systems (PID loop, cruise control, inverted pendulum), signal processing, electrical and physics models. Each entry gives an id, what the diagram does, its difficulty and…

• load_template

  Replaces the entire canvas with one of the built-in verified diagrams, by id from get_templates. The template carries its topology, parameters and simulation settings. Returns the block and connection counts, the verified simulation…

• run_simulation

  Triggers a new simulation run with the current canvas state and settings, refreshing the signal data.

• sweep_parameter

  Runs simulations across a list of values for one parameter, returning control quality metrics (IAE, overshoot, settling_time, steady_state_error) per value. Requires measureBlockId and setpoint.

• optimize_parameters

  Finds the optimal value for a single parameter using golden-section search. Minimizes IAE (integral absolute error), overshoot, or settling_time within a [min, max] range. Converges in about 10 simulations.

• optimize_multi_parameter

  Optimizes 2–6 parameters simultaneously using Nelder-Mead simplex search, for example Kp, Ki and Kd of a PID controller at once.

• auto_tune_pid

  Automatically tunes a PID controller using the Ziegler-Nichols ultimate cycle method. Finds the ultimate gain (Ku) and oscillation period (Tu) via binary search, then applies ZN formulas. No prior knowledge of the plant required.

• identify_fopdt

  Analyzes a step response from a plant to identify its First-Order Plus Dead Time (FOPDT) parameters: Gain (K), Time Constant (tau), and Dead Time (theta). Requires a completed simulation with a step input connected to the plant. Returns…

• start_optimization

  Start a parameter optimization job in the background.

• get_job_status

  Check the status and progress of a background job.

• cancel_job

  Cancel a running background job.

• list_jobs

  List all recent background jobs and their status.

• explain_simulation

  Analyze the last completed simulation and return a structured diagnosis: signal anomalies (NaN, divergence, oscillation), solver health (rejection rate, efficiency), algebraic loops, and optional stability margins. Returns JSON with…

• get_bode_data

  Computes magnitude and phase frequency response (Bode data) between two blocks. Traces path backwards from outputBlockId. Returns analytic response if the path contains only linear blocks, otherwise runs numerical sweep.

• get_fft_data

  Computes FFT (frequency spectrum) of a Scope signal. Returns frequencies and magnitudes.

• get_engine_status

  Returns the simulation engine status, including supported solvers, active background jobs, and compilation/WASM capabilities.

• generate_code

  Generates standalone production code (C++, Python, Rust) from the current canvas diagram. Returns structured code files, interfaces (inputs/outputs), execution order, and diagnostics.

• undo_last_ai_action

  Undoes the last canvas modification made by the AI (add block, connect, delete, update parameter).

• redo_last_ai_action

  Redoes the last undone canvas modification.

• get_ai_history

  Returns the list of recent canvas operations performed by the AI, showing what can be undone.