Concrete MCP Server

Concrete MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Concrete Section Properties AI MCP Server.

What you get

A Model Context Protocol Server for Reinforced Concrete Section Analysis

Setting it up

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Concrete is connected, these are the calls the assistant has available:

• rectangular_concrete_area_properties — Compute the rectangular concrete section geometric properties
• arbitrary_concrete_area_properties — Compute arbitrary concrete section geometric properties
• rectangular_concrete_bending_capacity — Compute the rectangular concrete section bending capacities (Mx+, Mx- and My) under the given axial load
• rect_concrete_axial_moment_x_points — Compute the rectangular concrete section axial - moment/bending (around X) interaction diagram points
• rect_concrete_axial_moment_y_points — Compute the rectangular concrete section axial - moment/bending (around Y) interaction diagram points
• rect_concrete_axial_moment_x_image — Plots the rectangular concrete section axial - moment/bending (around X) interaction diagram points
• rect_concrete_axial_moment_y_image — Plots the rectangular concrete section axial - moment/bending (around Y) interaction diagram points
• Requirements — The Requirements tool exposed by this server
• Guide — 1. Install the required Python libraries from the command line:
• Configuration — The configuration file is located at src/config.json and contains the following main settings:

Configuration and credentials

Required Python libraries:

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Concrete.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the concrete mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Concrete's toolset — rectangular_concrete_area_properties, arbitrary_concrete_area_properties, rectangular_concrete_bending_capacity and 7 more — is a fair guide to whether it matches your workflow. It is maintained by GreatApo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.