compute_combined_services_trench — civilquants MCP Tool
compute_combined_services_trench
(compute combined services trench) is one of 56 tools on the
civilquants
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compute_combined_services_trench from your client
- Claude Code civilquants compute_combined_services_trench run in your project directory
- Claude Desktop civilquants compute_combined_services_trench ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor civilquants compute_combined_services_trench ~/.cursor/mcp.json
- VS Code civilquants compute_combined_services_trench .vscode/mcp.json
- Zed civilquants compute_combined_services_trench ~/.config/zed/settings.json
- Windsurf civilquants compute_combined_services_trench ~/.codeium/windsurf/mcp_config.json
- Cline civilquants compute_combined_services_trench ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI civilquants compute_combined_services_trench ~/.gemini/settings.json
- Grok civilquants compute_combined_services_trench .mcp.json (in your project root)
- ChatGPT civilquants compute_combined_services_trench Settings → Connectors → Advanced → Developer mode
- Claude.ai civilquants compute_combined_services_trench Settings → Connectors → Add custom connector
- LangChain civilquants compute_combined_services_trench pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http civilquants https://api.civilquants.com/mcpOther tools on this server
- compute_connection_to_existing
- compute_hard_material_in_trench
- compute_ditch
- compute_pipework_testing
- compute_catchpit
- compute_manhole
- compute_manhole_precast
- compute_box_culvert
- compute_gully
- compute_headwall_attenuation_outlet
- compute_headwall_precast
- compute_headwall
- compute_carrier_pipe_run
- compute_french_drain
- compute_edge_drain
- compute_pipe_bedding
- compute_soakaway
- compute_attenuation_tank
- compute_swale
- compute_petrol_oil_interceptor
- compute_gabion_wall
- compute_reinforced_soil_wall
- compute_soil_nailed_slope
- compute_embankment_cross_section
- compute_end_area_earthworks
- compute_parapet
- compute_highway_drainage_channel
- compute_lighting_column
- compute_vehicle_restraint_system
- compute_road_marking
- compute_traffic_sign
- compute_flexible_pavement
- compute_permeable_pavement
- compute_rigid_pavement
- compute_anchored_wall
- compute_bored_pile_wall
- compute_cantilever_wall
- compute_counterfort_wall
- compute_gravity_wall
- compute_kerb_run
- compute_pad_foundation
- compute_strip_foundation
- compute_utility_chamber
- compute_utility_kiosk_base
- compute_single_service_run
- render_skill_report
- save_project
- get_project
- list_projects
- recompute_project
- compute_multi_section_assembly
- resolve_assembly_from_description
- list_skills
- get_skill
- get_document_pipeline
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.