Cbm

What cbm MCP server does

The cbm MCP server provides shipment-calculation capabilities centered on three inputs or outputs described by the listing: cargo volume, cargo weight, and container fit. It works with both cubic meters (CBM) and cubic feet (CFT), allowing an agent to reason about shipment size using either unit system. Its container-related calculation covers how cargo fits standard shipping containers.

The listed source is the Container Math developer API at containermath.com/developer-api. Based on the available description, the cbm MCP server is intended for logistics, freight, and shipment-planning workflows where an agent needs to estimate physical cargo requirements rather than retrieve general developer or business data.

A typical use would be asking an agent to calculate the volume of a shipment, convert or report that volume as CBM or CFT, account for cargo weight, and assess whether the cargo fits a standard shipping container. The supplied material does not specify the exact input schema, whether dimensions are accepted individually, or how multiple cargo items are represented.

Limitations and notes

The cbm MCP server listing does not include a README, so important implementation details cannot be confirmed from the available material. No installation command, package name, transport type, authentication method, environment variable, request format, response format, or version information is provided.

The description identifies standard shipping containers but does not enumerate container sizes or types. It also does not state whether the fit calculation accounts for packing orientation, unused space, weight limits, loading constraints, or irregular cargo shapes. Do not assume those behaviors without checking the linked developer API documentation.

Client compatibility is also unspecified. The available information does not name Claude Desktop, Cursor, or any other MCP client, so client-specific setup cannot be documented here. The cbm MCP server should be evaluated against the API documentation before implementation, especially if the workflow requires authentication, detailed packing rules, or a precise unit-conversion contract.

In short, the supported use case is clear at a high level: calculate shipment volume in CBM/CFT, calculate or use cargo weight, and assess fit in standard shipping containers. The supplied material is not sufficient to describe operational setup or more detailed logistics rules.