section_write_undo — MIDAS CIVIL NX tools (MIDAS IT Europe) MCP Tool
section_write_undo
(section write undo) is one of 108 tools on the
MIDAS CIVIL NX tools (MIDAS IT Europe)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call section_write_undo from your client
- Claude Code MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo run in your project directory
- Claude Desktop MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo ~/.cursor/mcp.json
- VS Code MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo .vscode/mcp.json
- Zed MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo ~/.config/zed/settings.json
- Windsurf MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo ~/.codeium/windsurf/mcp_config.json
- Cline MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo ~/.gemini/settings.json
- Grok MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo .mcp.json (in your project root)
- ChatGPT MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo Settings → Connectors → Advanced → Developer mode
- Claude.ai MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo Settings → Connectors → Add custom connector
- LangChain MIDAS CIVIL NX tools (MIDAS IT Europe) section_write_undo pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http civil-nx https://midasiteurope.com/mcpOther tools on this server
- auto_structure_groups
- auto_structure_groups_undo
- b2p_survey
- b2p_convert
- b2p_undo
- bridge_reshape_read
- bridge_reshape
- bridge_reshape_undo
- bridge_thermal_calc
- bridge_thermal_read
- bridge_thermal_apply
- bridge_thermal_undo
- bridge_thermal_remove
- concurrent_forces_setup
- concurrent_forces
- concurrent_forces_probe
- cs454_lane_layout
- cs454_moving_loads_read
- cs454_moving_loads
- cs454_moving_loads_undo
- cs454_combinations_read
- cs454_combinations_apply
- cs454_combinations_undo
- cs455_describe_section
- cs455_assess
- cs455_export_calc_sheet
- cs_stage_summary
- cs_stage_results
- cs_stage_report
- culvert_preview
- culvert_build
- culvert_build_undo
- culvert_analyse_and_check
- culvert_report
- midas_docs_search
- midas_docs_read
- dxf_inspect
- dxf_import
- dxf_import_undo
- ec_combinations_read
- ec_combinations_apply
- ec_combinations_undo
- ec_lane_layout
- ec_moving_loads_read
- ec_moving_loads
- ec_moving_loads_undo
- ec_wind_bridge
- ec_wind_read_deck
- ec_wind_apply
- ec_wind_remove
- skew_grillage
- skew_grillage_undo
- combination_tree
- combination_contributions
- midas_library
- civil_status
- civil_read_table
- job_status
- model_health_check
- model_qc_check
- model_report_images
- model_report_export
- model_bridge_summary
- model_to_ifc
- model_to_dxf
- create_nodes
- create_nodes_undo
- pd6694_route_a
- pd6694_route_a_write
- pd6694_route_a_remove
- pd6694_ssi_plan
- pd6694_ssi_run
- pd6694_ssi_remove
- point_to_patch_dispersal
- point_to_patch_read
- point_to_patch_apply
- point_to_patch_undo
- civil_loads_supports
- civil_combinations_quick
- civil_remove_loads
- slab_capacities_from_bars
- slab_survey
- slab_assess
- slab_explain_location
- result_table_catalog
- preview_result_table
- export_result_tables
- section_preview
- section_properties
- section_write
- section_read
- stage_groups
- construction_stages
- stages_undo
- stress_element_loads
- stress_profile
- sls_stress_check
- civil_write_tables
- civil_write_tables_undo
- civil_run_analysis
- civil_save_model
- tendon_design
- tendon_write
- tendon_write_undo
- ec2_describe_section
- ec2_section_check
- ec2_export_calc_sheet
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.