Thermal Mass Estimator MCP for AI. Simulate wall performance, from U-value to damping.

Q: estimatethermalbehavior only works on wood?

No. You use getmaterialproperties first to check if the MCP supports the thermal constants for whatever building material you're using, like concrete or brick.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

The Thermal Mass Estimator calculates how heat moves through building walls. It quantifies thermal lag, the degree of temperature fluctuation reduction (damping), and the U-value for various materials like brick or concrete.

You use this MCP to run complex physics calculations needed for energy modeling and envelope performance testing.

What your AI can do

Calculate u value

Calculates the thermal transmittance (U-value) for a single layer of building material.

Estimate thermal behavior

Projects how much temperature fluctuations are reduced and what the time delay is across a wall layer.

Get material properties

Retrieves fundamental thermal properties like conductivity, density, and specific heat for any listed material.

Determine fundamental material inputs

Retrieve core thermal properties (conductivity, density, specific heat) for building materials.

Calculate wall transmittance rates

Find the U-value, which measures how easily heat passes through a specific layer of material.

Project thermal time effects

Estimate both the time lag and the amplitude damping factor for heat moving through a structure.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

Thermal Mass Estimator: 3 Tools

These tools let you calculate the core physical properties of building materials, estimate their U-value, and project how they react to temperature changes over time.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Thermal Mass Estimator on Vinkius

Calculate U Value

Calculates the thermal transmittance (U-value) for a single layer of building material.

Estimate Thermal Behavior

Projects how much temperature fluctuations are reduced and what the time delay is...

Get Material Properties

Retrieves fundamental thermal properties like conductivity, density, and specific...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The Thermal Mass Estimator integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "thermal-mass-estimator": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the Thermal Mass Estimator tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"thermal-mass-estimator": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with Thermal Mass Estimator, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Thermal Mass Estimator. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Modeling building envelopes used to be a headache of spreadsheets and standards manuals.

Right now, calculating thermal performance means pulling material data from one database, running the simple U-value calculation in another spreadsheet, and then manually feeding that number into a third tool just to estimate the time delay. It's slow, it's tedious, and you always worry about which version of the constants sheet is current.

This MCP changes that workflow. You tell your agent what wall you have, and it pulls all necessary material properties first. Then, it runs a full physics model in sequence, giving you both the immediate U-value and the long-term thermal behavior—all in one go.

You Get Full Thermal Behavior Insights with `estimate_thermal_behavior`

Previously, assessing how much a structure actually dampens temperature swings required multiple complex equations and assumptions about material uniformity. You had to manually define the time variables and run separate iterative calculations.

Now, you ask for the thermal behavior, and it calculates both the amplitude damping factor and the time lag instantly. It's not just a number; it's a full performance projection.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

Building a structure requires more than just stacking bricks; you have to understand how heat moves through it over time. This MCP gives you specialized tools to quantify the thermal performance of any building envelope. Instead of running multiple spreadsheets and manually checking material constants, this connector pulls fundamental data—like conductivity and density—for materials such as concrete or brick.

Then, it uses those inputs to calculate a wall's precise thermal transmittance (U-value). You can also project how much temperature swings are dampened and what the time delay is for heat moving through the entire structure. Accessing this kind of specialized simulation power is usually hard work, but with Vinkius hosting this MCP in your catalog, you get reliable results directly into your workflow.

Built · Hosted · Managed by Vinkius Thermal Mass Estimator - U-value & Thermal Behavior

Server ID 019ed92a-b187-737e-a588-17fb3f5fbba4

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is, this lets you run full thermal simulations without leaving your agent environment.

First, run get_material_properties to pull the necessary thermal constants for your chosen building material.

Next, you feed those inputs into either calculate_u_value (for basic transmission) or estimate_thermal_behavior (for time-series analysis).

The MCP delivers the calculated performance metrics—like U-value and damping factor—allowing you to assess the structure's energy efficiency.

What Changes When You Connect

Determine if your proposed materials meet code. Use calculate_u_value to quickly check thermal transmittance for any layer thickness and material combination.

Model real-world heat dynamics. Run estimate_thermal_behavior to see how temperature fluctuations are reduced (damping) and what the time delay is (lag).

Avoid guesswork with inputs. Use get_material_properties to pull validated data points for conductivity, density, and specific heat capacity.

Speed up your design cycle. Instead of cross-referencing multiple textbooks, you get core physics calculations instantly from your agent.

Build better energy models. By linking the material properties with both U-value and thermal behavior, you create a complete picture of envelope performance.

See it in action

01 01

The client demands proof of low energy usage.

An architect needs to prove that using locally sourced brick reduces the building's total cooling load. They run get_material_properties on the brick, then use this MCP to calculate the U-value and estimate thermal behavior, presenting a clear data packet proving compliance.

02 02

The site has wildly fluctuating outdoor temperatures.

A mechanical engineer needs to know how quickly the wall structure will react to sudden weather shifts. They run estimate_thermal_behavior on a layer of concrete, getting precise data on thermal lag and damping that informs their HVAC sizing.

03 03

The initial material choice fails code compliance.

A building scientist discovers the current wall assembly exceeds local energy codes. They use calculate_u_value repeatedly with different thicknesses of insulation to find the minimum required change, saving weeks of manual calculation.

04 04

You need a single source for all thermal data.

Instead of gathering conductivity from one database and U-values from another, you send your agent to this MCP. It pulls get_material_properties first, then uses the output to run both calculate_u_value and estimate_thermal_behavior sequentially.

The honest tradeoffs

Treating U-value as enough.

Anti-pattern

Assuming that just because a wall has low conductivity, it will perform well in the long run. This overlooks how fast or slow heat actually moves through the structure.

The Fix

You must check both the basic transmission using calculate_u_value AND model the time effect with estimate_thermal_behavior. Only comparing U-value is incomplete.

Ignoring material constants.

Anti-pattern

Building a simulation based on generic values found online, without checking if they match the specific density or heat capacity of your local concrete mix.

The Fix

Always start by using get_material_properties. This ensures you are feeding the calculation engine with accurate data for your exact building material.

Mixing tools manually.

Anti-pattern

Calculating a U-value in one program, and then taking that number and trying to input it into a separate spreadsheet for thermal lag modeling. This introduces manual copy/paste errors.

The Fix

Let your agent handle the whole sequence. It can use get_material_properties and feed those results directly into both calculate_u_value and estimate_thermal_behavior without you lifting a finger.

When It Fits, When It Doesn't

Use this MCP if your job involves calculating heat transfer rates across building envelopes, particularly when time-dependent performance matters. If you need to know how fast or slow the structure reacts to temperature changes (the 'lag' or 'damping'), this is mandatory because a simple U-value calculation misses that critical dynamic information. Don't use it if you are only calculating basic static loads; for that, other tools might suffice. But never rely on just one metric; always check get_material_properties first to validate your inputs before running either calculate_u_value or estimate_thermal_behavior.

Questions you might have

How do I calculate U-value using the `calculate_u_value` tool? +

You provide the agent with the wall thickness and material type. The MCP runs the calculation, giving you the thermal transmittance value for that specific layer.

What is the difference between U-value and `estimate_thermal_behavior`? +

U-value is a static measure of heat transfer rate; it's what the wall transmits right now. estimate_thermal_behavior projects how that performance changes over time—the lag and damping.

Do I need to use `get_material_properties` before anything else? +

Yes, you should always start there. It ensures the MCP has the correct conductivity, density, and specific heat data for your material before it runs any calculations.

`estimate_thermal_behavior` only works on wood? +

No. You use get_material_properties first to check if the MCP supports the thermal constants for whatever building material you're using, like concrete or brick.

What units must I use when running `calculate_u_value` for wall thickness? +

It requires the thickness in meters. Always ensure your input measurements are standardized to SI units; otherwise, the resulting thermal transmittance will be inaccurate.

If I try to call `get_material_properties` with a material not recognized by the system, what happens? +

The tool returns an explicit error message and suggests checking your spelling or consulting the approved list of building compounds. You'll get a specific code indicating invalid input.

Can I use `calculate_u_value` to model complex, multi-material wall assemblies? +

No, it calculates U-values for single layers only. If your wall is made of several materials, you need to run the tool for each layer and average them manually.

Is there a rate limit on how often I can use `estimate_thermal_behavior`? +

The MCP supports high-volume usage for most clients. If you hit a temporary limit, the system will prompt you to wait; usually, thirty seconds is enough before retrying.

What materials are supported? +

The server currently supports brick, concrete, wood, and drywall.

How is the U-value calculated? +

The U-value is calculated as the ratio of the material's thermal conductivity to its thickness in meters.

What does thermal lag represent? +

Thermal lag represents the time interval between peak external temperature and peak internal temperature.

Connect to your AI in seconds.

Calculate u value

Estimate thermal behavior

Get material properties

Thermal Mass Estimator: 3 Tools

Make your AI actually useful.

Calculate U Value

Estimate Thermal Behavior

Get Material Properties

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Modeling building envelopes used to be a headache of spreadsheets and standards manuals.

You Get Full Thermal Behavior Insights with `estimate_thermal_behavior`

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

The client demands proof of low energy usage.

The site has wildly fluctuating outdoor temperatures.

The initial material choice fails code compliance.

You need a single source for all thermal data.

The honest tradeoffs

Treating U-value as enough.

Ignoring material constants.

Mixing tools manually.

When It Fits, When It Doesn't

Questions you might have