get_available_blocks — BlockWerk MCP Tool Read-only
get_available_blocks
(get available blocks) is one of 42 tools on the
BlockWerk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_available_blocks from your client
- Claude Code BlockWerk get_available_blocks run in your project directory
- Claude Desktop BlockWerk get_available_blocks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BlockWerk get_available_blocks ~/.cursor/mcp.json
- VS Code BlockWerk get_available_blocks .vscode/mcp.json
- Zed BlockWerk get_available_blocks ~/.config/zed/settings.json
- Windsurf BlockWerk get_available_blocks ~/.codeium/windsurf/mcp_config.json
- Cline BlockWerk get_available_blocks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BlockWerk get_available_blocks ~/.gemini/settings.json
- Grok BlockWerk get_available_blocks .mcp.json (in your project root)
- ChatGPT BlockWerk get_available_blocks Settings → Connectors → Advanced → Developer mode
- Claude.ai BlockWerk get_available_blocks Settings → Connectors → Add custom connector
- LangChain BlockWerk get_available_blocks pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://blockwerk-mcp-worker.blockwerk.workers.dev/Other tools on this server
- describe_canvas
- add_block
- connect_blocks
- update_params
- delete_block
- load_diagram
- export_diagram
- get_share_link
- clear_canvas
- tidy_layout
- batch_commands
- analyze_topology
- get_signal_data
- calculate_metrics
- get_analysis_measurements
- evaluate_spec_mask
- get_architect_memory
- update_architect_memory
- validate_engineering_units
- validate_canvas
- get_canvas_preview
- get_templates
- load_template
- run_simulation
- sweep_parameter
- optimize_parameters
- optimize_multi_parameter
- auto_tune_pid
- identify_fopdt
- start_optimization
- get_job_status
- cancel_job
- list_jobs
- explain_simulation
- get_bode_data
- get_fft_data
- get_engine_status
- generate_code
- undo_last_ai_action
- redo_last_ai_action
- get_ai_history
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.