https://blockwerk-mcp-worker.blockwerk.workers.dev/Custom connectors are available on every Claude plan; the Free plan allows one.
claude mcp add --transport http blockwerk https://blockwerk-mcp-worker.blockwerk.workers.dev/
Or install the BlockWerk plugin, which adds the connector together with a modelling skill and a /blockwerk:simulate command.
Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project:
{
"mcpServers": {
"blockwerk": { "url": "https://blockwerk-mcp-worker.blockwerk.workers.dev/" }
}
}
Add this to .vscode/mcp.json (or run MCP: Open User Configuration to add it for every workspace):
{
"servers": {
"blockwerk": { "type": "http", "url": "https://blockwerk-mcp-worker.blockwerk.workers.dev/" }
}
}
A project-level .mcp.json in the portable format uses "mcpServers" instead of "servers".
Open the agent window's (…) menu, choose Manage MCP Servers, click View raw config and add the server to mcp_config.json. Antigravity names the key serverUrl:
{
"mcpServers": {
"blockwerk": { "serverUrl": "https://blockwerk-mcp-worker.blockwerk.workers.dev/" }
}
}
gemini mcp add --transport http blockwerk https://blockwerk-mcp-worker.blockwerk.workers.dev/
Or edit settings.json and use httpUrl for streamable HTTP:
{
"mcpServers": {
"blockwerk": { "httpUrl": "https://blockwerk-mcp-worker.blockwerk.workers.dev/" }
}
}
codex mcp add blockwerk --url https://blockwerk-mcp-worker.blockwerk.workers.dev/
Or add it to ~/.codex/config.toml:
[mcp_servers.blockwerk] url = "https://blockwerk-mcp-worker.blockwerk.workers.dev/"
Add the remote server to opencode.json (or pair a live browser tab with type: "local" and npx -y @blockwerk/mcp-server --device <token>):
{
"mcp": {
"blockwerk": {
"type": "remote",
"url": "https://blockwerk-mcp-worker.blockwerk.workers.dev/",
"enabled": true
}
}
}
Turn on generative orchestration for your agent, then use the MCP onboarding wizard to connect an existing MCP server. Enter the server URL and choose no authentication. Copilot Studio reads the tool list from the server.
Any client that supports remote streamable HTTP servers works. Give it the server URL, with no authentication and no headers. Clients that only speak stdio can reach it through an HTTP bridge such as mcp-remote.
Without pairing, the server gives each connection a private scratch canvas. The assistant can build, inspect and export diagrams and hand you a share link. Simulations run in the browser, so tools that need results — running, measuring, tuning — return that share link instead: open it and press Run.
With pairing, every tool drives your own BlockWerk tab, including simulation. Open blockwerk.tech, click Connect AI in the assistant panel, and use the connector URL shown there. Keep the tab open while you work; you can revoke the pairing from the same panel.
Want a stable scratch canvas without pairing? Use https://blockwerk-mcp-worker.blockwerk.workers.dev/t/<any-id-of-20-characters-or-more>; the id keeps every request on the same canvas.
Paste any of these prompts directly into Claude, ChatGPT, Cursor, VS Code or any other connected assistant:
“Build a second-order mass-spring-damper system with m = 1 kg, k = 20 N/m and c = 2 Ns/m, simulate a step force and show the step response on a scope.”
“Tune the PID controller of this schema for a maximum overshoot of 5% and a rise time < 0.2s, then verify the closed-loop step response.”
“Run a parameter sweep over the resistance from 1 to 100 Ohm in 10 steps and report the peak voltage and settling time.”
| Kind | Examples |
|---|---|
| Read-only | describe_canvas, get_available_blocks, get_signal_data, calculate_metrics, get_bode_data, explain_simulation, generate_code |
| Edits | add_block, connect_blocks, update_params, tidy_layout, run_simulation, optimize_parameters, auto_tune_pid |
| Destructive | delete_block, clear_canvas, load_diagram, batch_commands, undo/redo |
When your tab is paired, delete_block, clear_canvas and load_diagram ask for your approval in BlockWerk before they run.
No account, name or email is needed. Scratch canvases are deleted after 24 hours without use; paired sessions are relayed end-to-end encrypted to your own tab. Details are in the Privacy Policy. Questions or problems: blockwerk.tech@outlook.com.