Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Steel Tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Steel takeoff, weight and gauge calculators plus RFQ, RFI, NCR and Bluebeam markup generators.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http steel-tools-mcp https://www.structupath.ai/api/mcp
# 2 — ask your agent for something these tools do
# steel_gauge_thickness, steel_plate_weight, steel_shape_weight and 11 more
Steel Tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http steel-tools-mcp https://www.structupath.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Look up sheet steel gauge thickness (gauges 3-28) in inches and mm with lb/ft², for plain, galvanized or stainless series. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gauge | integer | yes | Sheet steel gauge number, 3 through 28 |
| material | string | no | Gauge series — the same number is a different thickness each |
Compute carbon steel plate weight from thickness (decimal or fraction) and width/length in inches, with optional material cost via price_per_lb. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| thickness_in | yes | Plate thickness in inches — decimal or fraction ("3/4", "1-1/8") | |
| width_in | number | yes | Plate width in INCHES (a 4x8 ft plate is 48 x 96 in) |
| length_in | number | yes | Plate length in INCHES |
| price_per_lb | number | no | Optional material price in $/lb, to include a cost estimate |
Look up an AISC shape designation (W, C, MC, L, HSS, PIPE) for lb/ft, depth and area, with optional piece weight. 14th-Edition-era data. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| designation | string | yes | AISC designation, e.g. "W21X50", "HSS6X6X3/8", "L4X4X3/8" |
| length_ft | number | no | Optional piece length in feet, for a piece weight |
| qty | integer | no | Optional piece count |
Describe a structural steel connection type (behaviour, use, what goes wrong) by name, alias or slug — or look up a structural bolt grade (A325, A490, A307). Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name_or_slug | string | yes | Connection name, alias or slug (e.g. "clip angle", "base-plate") or a bolt grade (e.g. "A490") |
RCSC minimum pretension for A325/A490 structural bolts by diameter, with the turn-of-the-nut rotation when a bolt length is given. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dia | string | yes | Bolt diameter in inches — fraction ("3/4") or decimal (0.75) |
| length_in | number | no | Optional bolt length in inches, for the turn-of-the-nut rotation |
Steel pipe dimensions by NPS and schedule: OD, wall, inside diameter and lb/ft for schedules 5, 10, 40/STD, 80/XS, 160 and XXS. Omit the schedule to list them all. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nps | string | yes | Nominal pipe size, e.g. "2", "1/2", "1-1/4" |
| schedule | string | no | Optional schedule: "40", "80", "160", "STD", "XS", "XXS", "5", "10" |
Weight of round bar, square bar, flat bar or round tube from dimensions in inches — lb/ft and optional piece weight, in carbon, stainless or aluminum. For AISC designations use steel_shape_weight; for plate use steel_plate_weight. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | yes | Cross-section type |
| dim1_in | number | yes | First dimension in inches: diameter (round bar), side (square bar), width (flat bar) or OD (round tube) |
| dim2_in | number | no | Second dimension in inches: thickness (flat bar) or wall (round tube); unused for round and square bar |
| length_ft | number | no | Optional length in feet for a piece weight |
| material | string | no | Default carbon steel; stainless is +2%, aluminum ×0.35 |
Screen a mill cert's yield and tensile against the specified limits for A992, A572 Gr. 50 or A36 — a screening aid, not acceptance. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grade | string | yes | Steel grade: "A992", "A572 Gr. 50" or "A36" |
| yield_ksi | number | yes | Reported yield, ksi |
| tensile_ksi | number | yes | Reported tensile, ksi |
Roll a member list (AISC designation, length in feet, piece count — up to 500 lines) into a bill-of-steel ledger: weight per line, total pounds and tons, piece and lineal-foot counts. Net weight only; unmatched designations are listed, not guessed. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| members | array | yes | The member list to roll up, one line per mark/size |
Surface area to coat for an AISC shape: ft² per foot from the cross-section perimeter, piece/lot area with length and qty, optional interior faces for galvanized tubes and gallons at a supplied coverage rate. Published nominal values for estimating and orientation, not design guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| designation | string | yes | AISC designation, e.g. W21X50, HSS6X6X3/8, Pipe4STD |
| length_ft | number | no | Optional length in feet for a piece/lot area |
| qty | integer | no | Optional piece count (default 1) when a length is given |
| include_inside_faces | boolean | no | Tubes only: add interior surface, as hot-dip galvanizing coats vented HSS/pipe interiors. Default false (outside only). |
| coverage_sqft_per_gal | number | no | Optional practical coverage rate from the coating datasheet, to estimate gallons |
Generate a vendor-ready Request for Quotation (.xlsx) from structured takeoff line items — grouped by material, with vendor pricing columns, totals and standard terms. You pass parsed line items and a company name; returns a download link that expires within ~48 hours. Nothing you submit is stored.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | yes | Buyer company on the RFQ header and terms — required |
| company_location | string | no | City, state under the company name, e.g. "Denver, CO" |
| project_name | string | yes | Project name for the header and filename |
| project_location | string | no | — |
| date_issued | string | no | Free-form issue date; a blank line is used if omitted |
| line_items | array | yes | Parsed takeoff line items — the calling agent reads the estimate |
| nesting_rows | array | no | Optional fabricator-facing nesting/drop reference rows |
| terms | array | no | Override the eight default terms; omit for the standard set |
Add real Bluebeam-compatible annotation objects to a drawing PDF — counts, length/area measurements with live scales, RFI clouds, callouts — from a markups JSON you supply plus placement coordinates. Pass the PDF as an https URL or small base64; returns a marked PDF download link that expires within ~48 hours. Markups appear in Bluebeam Revu's Markups List. You decide placement; the tool guarantee
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pdf_url | string | no | HTTPS URL of the source drawing PDF (fetched server-side, SSRF-guarded) |
| pdf_base64 | string | no | Base64 PDF for small files (~3 MB max decoded); prefer pdf_url for drawing sets |
| markups | array | yes | Markups to place — geometry in ratio (0–1 from top-left) or pdf coordinates |
| scale | string | no | Document scale for measurements, e.g. "1/4 in = 1 ft" or "1:100" |
| page_scales | object | no | Per-page scale overrides, keyed by page number string |
| coordinate_space | string | no | — |
| author | string | no | Markups List author column |
Generate a formal Request for Information PDF from structured fields — header, meta grid, subject, description, proposed solution, attachments, and a blank response block for the design team. You do the judgement (one issue per RFI, exact drawing references, a proposed path forward); the tool guarantees the format. Returns a download link that expires within ~48 hours. Nothing you submit is stored
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | yes | Contractor issuing the RFI — appears in the header |
| company_location | string | no | — |
| rfi_number | string | yes | RFI number from the project register, e.g. "RFI-017" |
| date | string | yes | Submission date |
| project_name | string | yes | — |
| project_number | string | no | — |
| submitted_to | string | yes | The party who must respond — engineer, architect, GC |
| submitted_by | string | yes | Name — company |
| reason | string | no | Category: Design Omission, Design Error, Constructability Issue, Scope Clarification, Site Condition, Missing Information, Coordination Conflict — or free text |
| drawing_refs | array | no | Exact drawing numbers with revisions |
| spec_refs | array | no | — |
| subject | string | yes | One-line subject — one issue per RFI |
| description | string | yes | The issue: specific references, what is missing or conflicting, why it matters. Newlines respected. |
| proposed_solution | string | no | Suggested path forward, framed as a proposal |
| response_needed_by | string | no | — |
| attachments | array | no | — |
Generate a formal Nonconformance Report PDF: identification, description, the violated requirement, containment, root cause (prose or 5-Whys chain), disposition (accept-as-is/repair/rework/reject) with actions, and blank quality-review and sign-off blocks. Flags accept-as-is dispositions whose corrective action describes physical work. The disposition decision belongs to the responsible quality au
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | yes | Contractor raising the NCR — appears in the header |
| company_location | string | no | — |
| ncr_number | string | yes | NCR number from the project register, e.g. "NCR-008" |
| date | string | yes | Date raised |
| project_name | string | yes | — |
| project_number | string | no | — |
| raised_by | string | yes | Name — role |
| trade_or_supplier | string | no | — |
| location | string | no | Area, level, grid, or piece mark |
| description | string | yes | What was found, measured against what was required |
| requirement_violated | string | yes | The cited requirement — spec section, drawing/detail, or code clause. An NCR without a cited requirement is dispute fuel. |
| containment | string | no | What was done on the spot — quarantine, stop work, tag |
| root_cause | string | no | — |
| root_cause_whys | array | no | 5-Whys chain, first why to root; overrides root_cause |
| resolution | string | yes | Disposition: accept-as-is (no physical work), repair, rework, or reject |
| resolution_justification | string | no | Required in practice for accept-as-is — the concession basis |
| corrective_action | string | no | Bringing this instance into compliance |
| preventive_action | string | no | Stopping recurrence — procedure, inspection, supplier |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Steel Tools or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.7.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Steel Tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.