CargoEffe MCP Server
Connect AI assistants (Claude Desktop, Claude Code, Cursor) to CargoEffe for automated cargo loading plan design.
Installation
# Option A: pip install
pip install cargoeffe-mcp
# Option B: uvx (no pre-install needed)
uvx cargoeffe-mcp
# Option C: from source
git clone https://github.com/dollob/cargoeffe-mcp.git
cd cargoeffe-mcp && pip install -e .
Setup
- Get your MCP token from CargoEffe Settings → MCP Tokens
- Configure your AI client:
Claude Code
{
"mcpServers": {
"cargoeffe": {
"command": "uvx",
"args": ["cargoeffe-mcp"],
"env": {
"CARGOEFFE_MCP_TOKEN": "cfm_YOUR_TOKEN_HERE"
}
}
}
}
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"cargoeffe": {
"command": "python",
"args": ["-m", "cargoeffe_mcp.server"],
"env": {
"CARGOEFFE_MCP_TOKEN": "cfm_YOUR_TOKEN_HERE"
}
}
}
}
Debug Mode
Set CARGOEFFE_MCP_DEBUG=true for verbose logging:
{
"env": {
"CARGOEFFE_MCP_TOKEN": "cfm_...",
"CARGOEFFE_MCP_DEBUG": "true"
}
}
Debug logs appear on stderr (visible in Claude Code's MCP debug panel).
Available Tools
| Tool | Description |
|---|---|
get_context |
Read CargoEffe system context (coordinates, rules) — free |
get_axle_templates |
List axle templates with weight limits — free |
plan_create |
Create a new load plan |
plan_load |
Load plan by ID |
plan_list |
List your plans |
plan_save |
Save plan to backend |
container_list |
List available containers |
container_set |
Set container for a plan |
cargo_add |
Add cargo items (bulk) |
cargo_list |
List cargo items |
cargo_update |
Update cargo properties |
cargo_remove |
Delete cargo + placements |
group_create |
Create loading group |
group_list |
List loading groups |
group_update |
Rename/reorder groups |
save_placements |
Save AI-calculated placements |
weight_check |
Get weight distribution analysis |
pallet_pack_list |
List available pallet packs |
pallet_pack_create |
Build a pallet pack from boxes |
pallet_pack_place |
Place a pallet pack into a plan |
Security
This package is a thin protocol bridge — it contains NO business logic, database queries, or API secrets. All sensitive operations happen on the CargoEffe backend.
License
MIT
Metadata
Release files for cargoeffe-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cargoeffe_mcp-0.3.0.tar.gz | 12.2 kB | Without provenance | Details for cargoeffe_mcp-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cargoeffe_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for cargoeffe_mcp-0.3.0-py3-none-any.whl |
Total release size: 25.6 kB
Release files / cargoeffe_mcp-0.3.0.tar.gz
| Download URL | cargoeffe_mcp-0.3.0.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1f392842072883fe290bab2fbe195c1a0de94538ca0ec4f13b49509bfc3eefe
|
|
BLAKE2b-256 checksum How to use checksums |
a660cd81a6f582d10a17d3e804d100d4c0c29840ce6542c12f172f8d6262cf1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / cargoeffe_mcp-0.3.0-py3-none-any.whl
| Download URL | cargoeffe_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54dcab2527b462d55a83a43e5e5cdca4d998782e12128337d557869fcf965d28
|
|
BLAKE2b-256 checksum How to use checksums |
627423cb2ce850f76b9ea3b9fe0c64136d1581ee58a7a1a62d446abaf1aeb9cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for cargoeffe-mcp 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.