Skip to main content
Glama
Kubova-com

@kubova/mcp

Official
by Kubova-com

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KUBOVA_API_KEYYesYour Kubova API key. Required. Generated from the dashboard at https://kubova.com/dashboard/api-keys.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pack_containersA

Pack a list of cargo SKUs into one or more shipping containers using the Kubova solver. Returns per-container placements with x,y,z coordinates in cm, volume utilization, weight, and any unplaced pieces.

generate_reportA

Generate a CAD-style PDF + 3D PNG report for a packing job. IMPORTANT: to keep the report consistent with a plan you already produced, pass the result object from your previous pack_containers call — the report then renders that exact plan instead of recomputing (which can differ run-to-run). If result is omitted, it packs from cargos + containers. Returns base64-encoded PDF + PNG per container plus the pack result.

estimate_capacityA

How many complete SETS of one product fit in a single container? A product is 1+ carton types with qtyPerSet each (e.g. a table shipping as 2 cartons: top + legs). All cartons of a set ride in the SAME container. Uses real 3D packing (not just volume math) and reports the binding limit (dimension/weight/volume) per container. Omit containers to evaluate the standard 20' DC, 40' DC, 40' HC.

verify_keyA

Verify the configured API key. Returns the key identity, scopes, and rate limit.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: capacity estimation, container packing, report generation, and API key verification; no overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: estimate_capacity, generate_report, pack_containers, verify_key.

Tool Count5/5

With 4 tools, the server is well-scoped for its packing optimization domain; each tool serves a core function without redundancy.

Completeness4/5

Covers the main workflow (estimate, pack, report) but lacks tools for managing containers or cargo definitions, though these may be handled via parameters.

Maintenance

ActivityInactive
ResponsivenessNo issues