Find your next source.

Useful for

Use cases llm-inferred

Desk-based site context overview (terrain, imagery, nearby live signals) before a site visit · Weather context review for an event window using forecast wind and observed radar replay · Visual briefing material for client and stakeholder presentations using scene capture

Audience llm-inferred

GIS analysts · flood consultants (visualisation only) · planners · civils/BIM engineers (visualisation only)

Limitations

Constraints llm-inferred

Traffic is simulated along real roads from aggregate location data, not measured · CCTV camera poses and rocket launch trajectories are coarse estimates · Public camera feeds only over listed regions · Google Maps and Cesium ion features are subject to provider terms and quotas · Voice control requires an OpenAI key · Bundled Nepal flood data is non-commercial only · Licence listed as Other, so reuse terms need checking before commercial use · Older versions no longer work with OpenStreetMap data sources and need updating

Useful for

Use cases llm-inferred

Model QA: list levels and elevations to check floor levels and invert assumptions against drainage or civils design · Parameter completeness check: colour-splash elements by parameter value to spot missing data before issue · Coordination drawings: export named Revit views as images for design review or client markup

Audience llm-inferred

BIM/civils engineers · BIM coordinators · Drainage and civils engineers using Revit · Python developers extending Revit automation

Limitations

Constraints docs-verified

Not yet Autodesk Marketplace certified · Requires desktop Revit running with pyRevit Routes active · Bridge accepts loopback hosts only; remote VM/LAN not supported · Docs status table marks 10 of the listed tools as Pending (e.g. create_line_based_element, delete_elements, modify_element) · Docs say the review candidate has 20 tools, but catalogue metadata lists 30 · pyRevit Routes API is in draft form and subject to change · execute_revit_code runs arbitrary Python; model-changing requests need in-Revit review

Useful for

Use cases llm-inferred

Pre-issue model check before sheet issue (revit_pre_issue_check) · Model audit of a Revit project for QA (revit_model_audit) · Drawing and sheet layout automation for issue sets (revit_drawing_layout) · Stair modelling and checks (revit_stairs)

Audience llm-inferred

BIM coordinators · BIM/civils engineers · Revit modellers

Limitations

Constraints llm-inferred

Windows only: the installer and PowerShell setup target a Windows machine · Revit must be open with a model, and MCP must be started from the ribbon each session · Revit versions limited to 2022–2027 · Early implementation, researched and implemented since March 2026 · Family Editor authoring is out of scope · Local only: no remote access; connects to Revit via localhost TCP (≤2024) or a named pipe (≥2025)

Useful for

Use cases llm-inferred

Pre-issue QA: audit view and sheet naming conventions across a drainage or civils model · Schedule checks: pull schedule rows and compare schedules for quantity reconciliation · Parameter QA: read element properties and flag missing values before exporting data · Visual review: export a view image of a drainage run or structure for markup in a design review

Audience llm-inferred

BIM/civils engineers · BIM managers and coordinators · drainage engineers · BIM/CAD technicians

Limitations

Constraints llm-inferred

Needs a live Revit session with a project open; no offline or file-based access · Requires pyRevit and the Revit Routes server enabled · Web UI binds to 127.0.0.1 by default; LAN sharing is for trusted networks only · Claude Desktop local MCP runs on one machine only · Schedule formula text is unsupported (public Revit 2024 API only) · Install instructions are Windows-specific · Tool argument schemas are not documented in DOCS

Useful for

Use cases llm-inferred

Model QA before design coordination: list Revit warnings and the affected element IDs · Parameter corrections on drainage or structural elements, applied only after human-approved plans · Read-only IFC storey and property checks on consultant models without opening Revit

Audience llm-inferred

BIM coordinators · BIM managers · BIM/civils engineers

Limitations

Constraints docs-verified

Pre-release: nothing has been verified in a live Revit session yet · Describes the dev branch; the latest GitHub release may not include all features · Live Revit work limited to Windows and Revit 2024 to 2027 · Approving a plan changes the open model; test on a copy first · Snapshot QA/QC and report modules need snapshot_id; model_bloat lacks the guard · Advanced tools (revit_execute_python, revit_invoke_method) have the full permissions of the Revit process · Navisworks support is in progress · No UK-specific standards, datasets or civils tooling described in the docs

Useful for

Use cases llm-inferred

Slope and aspect from a site DEM for drainage or earthworks setting-out (raster_operations) · Overlay and dissolve constraint layers such as flood zones and site boundaries in a project GDB (geometry_analysis) · Hot-spot or kernel density analysis of flood or incident records (spatial_statistics) · Export PDF/PNG map plates for planning or flood risk assessment submissions (export_layout)

Audience llm-inferred

GIS analysts · drainage engineers · hydrologists · civils/BIM engineers · planners

Limitations

Constraints docs-verified

Windows only; needs a licensed ArcGIS Pro installation and its Python environment set as ARCPY_PYTHON_PATH · Automated tests use mocked arcpy; the 100 geoprocessing tools are not validated across scenarios on a licensed runtime · Ten state-mutating tools (e.g. delete_dataset, repair_geometry) refuse to run without confirm: true · Some tools need Esri Spatial or Network extension licences · Sketch-to-GIS demo is marked 'coming soon'

Useful for

Use cases llm-inferred

Tender technical-bid compliance matrix, missing-document list and bid-risk flags from tender files (aios-tender-audit) · Special construction scheme review: hazard list, disclosure points and calculation-sheet gaps (aios-scheme-audit) · Building a norm-excerpt Knowledge Pack with citations for internal lookup (aios-knowledge)

Audience llm-inferred

construction tender and technical-bid staff · project document controllers · technical leads for construction schemes · AI/software teams building construction tools

Limitations

Constraints docs-verified

Knowledge Pack is not a production-grade norms database · Does not replace legal, chief engineer, expert, review or registered-professional sign-off · Docs describe Chinese-language construction workflows; no UK standards, water or civils coverage is documented · Not intended for non-construction tasks; outputs need human review

Useful for

Use cases llm-inferred

Preflight-checked inspection and summary of existing DWG drawings before civils or drainage design review · Guarded, dry-run-verified layer, annotation and dimension clean-up of CAD deliverables before issue · Generating PDF plot and PNG visual evidence of drainage or civils layouts for internal QA

Audience llm-inferred

civils engineers · drainage engineers · BIM and CAD technicians · GIS and CAD analysts

Limitations

Constraints docs-verified

Beta software, intended for controlled local use with operator review rather than unattended changes to production drawings · Windows only; requires AutoCAD running as the same Windows user · Not claimed to comply with formal ISO, GB or ASME standards · Requires a local MCP client; no hosted or remote operation

Useful for

Use cases llm-inferred

Flood zone, permit and code-case screening for a site due-diligence note · Zoning, lot dimensions and municipal code text lookup for a pre-application brief · Tree-permit and roadway work-zone check before site clearance or access planning · Special-district (MUD/PID) and appraisal context for a development or drainage-authority brief

Audience llm-inferred

flood consultants · planners · civils engineers · GIS analysts

Limitations

Constraints llm-inferred

Austin, Texas and Travis, Williamson and Hays counties only; no UK data, so relevance to a UK consultancy is low, although the catalogue lists regions as Global · Early-stage project run by a single maintainer, so expect gaps and possible breaking changes · MLS data covers active and under-contract listings only, with no sold comps · Listings, neighbourhood and blog content depend on neuhausre.com and the Neuhaus VOW API · Socrata rate limits apply unless an app token is set · Commute tool uses demo routing servers with no real-time traffic · Catalogue auth field says an API key is required, but docs say no key is needed · Catalogue tool list does not match docs: docs state 43 tools and list austin_utility_providers, austin_relocation, austin_local_voices and austin_health, which are absent from the metadata, while the metadata lists health_check

Useful for

Use cases llm-inferred

Prioritise open Navisworks clashes before a coordination meeting · Collapse repeated clashes to root-cause groups for trade discussions · Compare issue status between successive federated model deliveries · Prepare coordination work packages with trade ownership and PDF report images

Audience llm-inferred

BIM coordinators · BIM/civils engineers · design coordination managers

Limitations

Constraints docs-verified

Live coordination requires Windows and a licensed Autodesk Navisworks Manage 2024, 2025 or 2026 · Engineering approval and edits remain with the project team · Movement alternatives use element bounds and must be checked against surrounding geometry and design constraints · Revit and Power BI handoff relies on separate Horizun MCP servers

Useful for

Use cases llm-inferred

Flood-zone constraint screening for a project area using fema_nfhl · Soil and farmland siting indicators for drainage or SuDS options using nrcs_soils · Species and critical-habitat screening for early ecological constraints using ipac · Composite constraints map of a project area for early site appraisal using map_composer

Audience llm-inferred

GIS analysts · flood consultants · ecologists · planners · civils and BIM engineers

Limitations

Constraints docs-verified

Screening and research aid only; does not make legal or agency determinations or replace agency or Tribal consultation · Does not guarantee that upstream datasets are complete or current · map_composer queries public GIS services at request time, so results depend on those services being available · census and epa_aqs return no data until their credentials are set

Example tool calls docs-verified

{
  "tool": "ipac",
  "arguments": {
    "roi": "<project-area geometry; parameter name not stated in DOCS>"
  }
}

Useful for

Use cases llm-inferred

Tide and surge levels at Dutch coastal sites for marine works or outfall boundary checks (tides_nl) · Wind and wave forecast windows for coastal survey or dredging campaign planning · Bridge clearance and fairway depth checks for barge or crane access routes (fairway_nl)

Audience llm-inferred

coastal and marine engineers · hydrologists · civils and BIM engineers planning marine logistics · GIS analysts

Limitations

Constraints llm-inferred

Built and documented for recreational sailing, not engineering or regulatory use · Official charts, almanacs and notices must be checked before relying on outputs · Windy, WorldTides, Stormglass and AISStream need user-supplied API keys; keyed tools only appear when the key is present · AISStream is community-fed and sparse mid-ocean · Some bridges may show '(name unknown)' where OSM has no nearby named bridge · All tool times are UTC · Depends on third-party public endpoints (RWS, NDW, OSM/Overpass, aviationweather.gov, Open-Meteo) with no stated SLA · No public hosted endpoint is documented; the user must run or host an instance (docs use a 'your-host' placeholder) · ENTRY metadata lists OAuth, but DOCS describe API-key URL parameters and state 'No OAuth required' for Claude.ai · Likely single-maintainer personal project ('Built by @ai_kulikov'), so maintenance risk

Useful for

Use cases llm-inferred

Cut/fill earthwork volumes between existing ground and finished grade surfaces · Watershed delineation and Rational Method runoff checks for site drainage · Pipe network layout and hydraulic analysis for drainage design · Plan/profile sheet production and PDF publishing for design submissions

Audience llm-inferred

civil/highway design engineers · drainage engineers · hydrologists · BIM/civils engineers

Limitations

Constraints docs-verified

Requires a licensed local Civil 3D 2026 installation and Autodesk API references; Autodesk binaries are not shipped with the repo · Setup docs are Windows-focused (PowerShell commands, Civil 3D plugin built with .NET 8 on Windows) · The Civil 3D plugin must be loaded in a running Civil 3D session for drawing operations · Default MCP surface exposes 34 tools; the full 219-tool surface needs CIVIL3D_ENABLE_TOOL_ALIASES enabled · Entry lists 180 tools, which does not match the 34 public / 219 registered counts in the docs · Destructive or file-writing actions require the preview, approval-token, retry flow · Autodesk-hosted tutorial video playback requires internet access

Useful for

Use cases llm-inferred

Read-only audit of surfaces, alignments and COGO points with their layers before issuing a drawing · Scripted extraction of surface and alignment station/offset data for a drainage or highway design check · Batch creation of repetitive civils objects from skill templates in a design workflow

Audience llm-inferred

civils BIM engineers · drainage engineers · highway engineers · CAD technicians

Limitations

Constraints llm-inferred

Requires Autodesk Civil 3D to be running with the plugin loaded (NETLOAD, C3DMCPSTATUS to verify) · civil3d_execute modifies the drawing and commits the transaction · Roslyn sandbox blocks process execution, file deletion, network requests, registry access and dynamic assembly loading · Default execution timeout is 120000 ms · Argument names for the three tools are not documented in DOCS; the code parameter name in example_tool_calls is inferred · Code is AI-generated and runs with full Civil 3D API access, so output needs review before use on live drawings · Windows and Civil 3D version requirements are not stated in DOCS

Useful for

Use cases llm-inferred

Flag broken layer data sources in a client's ArcGIS Pro project before issuing mapping outputs · Inventory feature classes, fields and spatial reference in a .gdb before data handover or reuse · Run scripted ArcPy buffer or clip of site or watercourse layers for a constraints map · Check layouts and map frames in an .aprx project before reissuing a report figure set

Audience llm-inferred

GIS analysts · civils and drainage engineers working from ArcGIS Pro data · environmental consultants

Limitations

Constraints docs-verified

Windows only · Requires ArcGIS Pro to be installed and launchable; arcpy is not installed via uv · Not for publicly exposed remote GIS services · Not for unattended direct edits to production data · Not a replacement for the ArcGIS Pro GUI and not a general file-system tool · ArcGISProject('CURRENT') may fail to attach; pass the .aprx path instead · Lock errors if layers are being edited or data is in use by ArcGIS Pro · execute_arcpy_code runs code on the local machine; use only on trusted computers · Long or large jobs may time out; narrow scope or raise timeout_seconds · Stdio server is launched by the MCP client, not run manually as a desktop app

Useful for

Use cases llm-inferred

Urban baseline assembly from OpenStreetMap and Sentinel-2 for a site appraisal · Street-level imagery review of existing highway or drainage assets via Mapillary · LLM-assisted querying of geospatial urban datasets for desk-study reporting

Audience llm-inferred

GIS analysts · civils/BIM engineers · planners

Limitations

Constraints llm-inferred

ENTRY metadata lists no tools, so MCP tool names cannot be documented · DOCS describe a Python toolkit; MCP transport is not stated · Pilot-country focus in DOCS; UK coverage is not stated · Requires Copernicus CDSE and Mapillary credentials per ENTRY metadata · DOCS state no data resolution, update cadence or time span

Useful for

Use cases llm-inferred

DEM and orthomosaic production from drone survey photos for site topographic baselines · Ground-classified point clouds and surface models from UAV photogrammetry for earthworks or cut-fill inputs · Survey-grade models controlled with ground control points and coded markers · Batch export of DEM, orthomosaic and point cloud deliverables as GeoTIFF or LAZ for GIS and BIM handover

Audience llm-inferred

drone survey and photogrammetry consultants · GIS analysts · civils and BIM engineers · terrain and heritage 3D modellers

Limitations

Constraints llm-inferred

Runs inside a licensed desktop Metashape Professional 2.3+ session; not a standalone data source · Viewport and screenshot tools are unavailable in headless mode · Direct HTTP connection from Claude Code times out after about 60 seconds; the stdio proxy is needed for long jobs and requires a separate FastMCP install · ENTRY tool names (aerial_survey_pipeline, close_range_pipeline, batch_export, diagnose_alignment, optimize_quality_settings) match the docs' guided workflow prompts, not documented callable tools · Tool argument schemas are not documented in the DOCS text · No credentials documented in README; the Metashape licence is separate from the MIT-licensed server

Useful for

Use cases llm-inferred

Export print-quality layouts and Map Series from an ArcGIS Pro project for consultation or planning reports · Run clip, buffer or intersect geoprocessing on site or catchment layers and add outputs to the live map for review · Query layer attributes to build constraint or receptor tables for an assessment · Let an agent assemble and symbolise a thematic map in the open project while the consultant watches

Audience llm-inferred

GIS analysts · flood risk consultants · drainage engineers · planners · ecologists

Limitations

Constraints docs-verified

Requires a licensed ArcGIS Pro install; no ArcPy outside Pro · Live bridge needs the .NET add-in built and installed in Pro, plus MCP registration · Verified only on ArcGIS Pro 3.4 / ArcPy 3.4.3 / .NET 8 · Cartographic authoring (symbology, layout, layer management) is still an open frontier on the roadmap · Noncommercial licence; commercial use needs a paid licence · Tool arguments and parameter names are not documented in the README

Useful for

Use cases llm-inferred

Translate and rewrite foreign-language notes and callouts in place on construction drawing sheets · Batch-update layers, colours and text annotations across a drawing set · Export DWG drawings to DXF for downstream CAD or GIS exchange · Read block attributes and layer structure to audit drawing standards

Audience llm-inferred

BIM/civils engineers · CAD technicians · drainage engineers · GIS analysts

Limitations

Constraints llm-inferred

Windows-only installer (PowerShell, %APPDATA% and %LOCALAPPDATA% paths) · Requires an AutoCAD session running with the plugin loaded; not standalone · Only AutoCAD 2022-2027 is supported; other years need the plugin built from source · The v1.0.0 ZIP ships only the 2024 and 2027 plugin years · dwg_run_lisp refuses every request; dwg_send_code accepts inline synchronous snippets only · Installer requires AutoCAD to be closed · Health and update-check features are marked Unreleased · Usage evidence is limited to 220 tool calls over 19 days on one project

Useful for

Use cases llm-inferred

Parametric wall, slab and roof creation in an IFC model from natural-language prompts · Scene and object property review of an IFC model via get_ifc_scene_overview and get_object_info · Converting Trimesh-generated custom geometry into native IFC elements for civils BIM models · Screenshot-based QA of BIM model state in Blender

Audience llm-inferred

BIM/civils engineers · BIM coordinators · architects

Limitations

Constraints llm-inferred

Requires a local Blender 4.4+ installation with the Bonsai add-on and the BlenderMCP add-on connected · An empty IFC file must be saved before operations, otherwise changes do not reach the Blender scene · The general execute_code tool is unreliable for IFC operations and may be disabled · Knowledge base features need a local ChromaDB index and an embedding server · The author points users to a newer repository (bonsai-mcp) with a stronger code-generation focus, so this repo may receive less maintenance · Not an official Blender, Bonsai or IfcOpenShell project

Useful for

Use cases llm-inferred

Clash detection between structural and services models before design freeze · Model health audit and warnings review before issuing a model to a client · Material takeoff quantities for early cost estimates · Batch export of sheets to PDF, DWG or IFC for coordination submissions

Audience llm-inferred

BIM/civils engineers · BIM coordinators · structural engineers

Limitations

Constraints llm-inferred

Windows only: Revit runs only on Windows; macOS/Linux are not supported · Operates on the active document only; background documents are not accessible · Revit must be running with the TCP server started via Revit MCP Switch · TCP port 8080 must be free; the server will not start if it is occupied · No undo integration; AI operations are not grouped into a single undo step · send_code_to_revit may fail on assembly conflicts from third-party addins · Parameter names are localised; use BuiltInCategory names for categories · Requires Node.js 18+ for the MCP server · DOCS state both 138 and 124 tools; counts are unreconciled · Fork of an upstream project; maintenance risk

Useful for

Use cases llm-inferred

Batch-editing IFC property sets and bulk classification of Vectorworks BIM models · Generating criteria-driven schedules and reports from a Vectorworks drawing for civils or drainage deliverables · Georeferencing a drawing and converting lat/lon to drawing coordinates via EPSG codes for site layouts

Audience llm-inferred

BIM and civils engineers using Vectorworks 2026 · GIS analysts · CAD/BIM technicians scripting Vectorworks

Limitations

Constraints docs-verified

Every vs.* call runs on the Vectorworks main thread, so long operations block the UI · Export/import verbs (e.g. export_pdf, import_dwg) open Vectorworks modal settings dialogs with no headless path · File-IPC path is Windows-only; macOS/remote use needs the legacy TCP bridge (VWX_TRANSPORT=tcp) · Bridge runs only while the Vectorworks palette is open; closing or pausing it stops the bridge · Multi-step one-time Windows setup: native C++ palette build, menu command and shortcut

Example tool calls docs-verified

{
  "tool": "ping",
  "arguments": {}
}

Useful for

Use cases llm-inferred

Generating headless DXF drawing outputs for drainage or civils sheets on machines without AutoCAD (ezdxf backend) · Batch-updating title-block or equipment tag attributes across a set of drawings · Drafting P&ID-style process schematics for water treatment schemes with CTO symbols · Exporting drawings to DXF and PDF for issue to design teams or clients

Audience llm-inferred

CAD technicians · drainage engineers · civils and BIM engineers · process engineers drafting P&IDs

Limitations

Constraints docs-verified

File IPC backend needs Windows 10/11, native Windows Python 3.10+, and AutoCAD LT 2024 or newer running · AutoLISP is not supported on AutoCAD LT for Mac · offset, fillet and chamfer are File IPC only · execute_lisp is File IPC only · plot_pdf and undo/redo are not available on the ezdxf backend · P&ID symbol insertion requires the CTO P&ID Symbol Library installed at C:\PIDv4-CTO\ · Beta-style v3.1 release with IPC timing dependencies (timeout 1-300 s)

Example tool calls docs-verified

{
  "tool": "system",
  "arguments": {
    "operation": "status"
  }
}

{
  "tool": "drawing",
  "arguments": {
    "operation": "save_as_dxf"
  }
}

{
  "tool": "view",
  "arguments": {
    "operation": "get_screenshot"
  }
}

Useful for

Use cases llm-inferred

DCMA-14 schedule quality check on a civils programme before issue · P80 schedule risk contingency from Monte Carlo analysis of a construction programme · Period earned value and status reporting (SPI, CPI, EAC, forecast finish) against a baseline · Linking schedule tasks to BIM model elements by shared code for 4D sequencing

Audience llm-inferred

project controls and PMO staff · programme managers · planners and scheduling engineers · BIM/civils engineers

Limitations

Constraints docs-verified

write_native_mpp is unavailable on the file backend; without Microsoft Project the save falls back to MSPDI · level_resources refuses on the file backend rather than approximating Microsoft Project's leveller · Moving a task to another position in the outline is not offered · Tool schemas add about 13,500 tokens to every prompt while the server is connected

Useful for

Use cases llm-inferred

Cut/fill earthwork estimate for a linear corridor scheme (computeCorridorEarthwork) · Draft site grading and cut/fill balance for a development platform (optimizeGrading) · Batch editing of layers, blocks and entities across a drawing from natural language · Converting a raster site plan or sketch into CAD linework for further design

Audience llm-inferred

civil design engineers using Civil 3D · drainage engineers · BIM and civils CAD technicians

Limitations

Constraints docs-verified

Windows only · Needs a licensed AutoCAD/Civil 3D session open; plugin DLL is locked while C3D runs · Not an Autodesk product and not endorsed by Autodesk · Docs and default UI are Chinese; English UI added in v1.4.0 · No UK datasets, standards or geographic coverage stated · Docs cite both 270 and 274 MCP tools, so tool count may be inconsistent · 12 methods use a command channel with a 25 s timeout; some C3D features are not exposed to the AI · Corridor regeneration can take 30 s to 10 min and queues other requests (HOST_BUSY) · Grading optimisation is a draft generator; multi-level walls and pipe avoidance need manual review · Not a data API: no hydrology, gauge or DEM feeds documented

Example tool calls docs-verified

{
  "tool": "summarizeDrawing",
  "arguments": {}
}

{
  "tool": "computeCorridorEarthwork",
  "arguments": {}
}

{
  "tool": "optimizeGrading",
  "arguments": {}
}