Mcp Coordinadora
Hook Colombia’s Coordinadora courier into your stack so agents can quote shipments, create labels, or track parcels for your store or logistics tooling.
Overview
io.github.codespar/mcp-coordinadora is a MCP server for the Build phase that exposes Coordinadora Colombian courier and logistics APIs to coding agents.
What is this MCP server?
- Stdio MCP @codespar/mcp-coordinadora v0.1.0 for Colombian logistics
- Requires COORDINADORA_API_KEY and COORDINADORA_NIT company identifier
- From codespar/mcp-dev-latam packages/colombia/coordinadora
- Agent-facing tools over Model Context Protocol stdio transport
- Targets Coordinadora courier operations for Colombia
- Server version 0.1.0
- Two required env vars: API key (secret) and NIT (non-secret)
- stdio npm identifier @codespar/mcp-coordinadora
Community signal: 252 GitHub stars.
What problem does it solve?
Shipping integrations for Colombia stall on carrier credentials, NIT setup, and repetitive API experimentation while you are still building the product.
Who is it for?
Indie ecommerce or logistics apps serving Colombia with an existing Coordinadora account and NIT on file.
Skip if: Global-only shops with no Colombian fulfillment, or builders who only need generic shipping mocks.
What do I get? / Deliverables
Once configured, your agent can call Coordinadora through MCP so fulfillment features ship faster with fewer context switches to carrier documentation.
- MCP-connected Coordinadora tooling in your dev agent
- Implementation paths for rates, labels, or tracking
- Colombia-specific fulfillment integration baseline
Recommended MCP Servers
Journey fit
Courier MCP servers are Build-phase integration tools that connect shipping logic while you implement checkout and fulfillment. Logistics APIs belong in integrations alongside payment and inventory connectors your agent orchestrates.
How it compares
Colombia-specific carrier MCP integration, not a multi-carrier abstraction library.
Common Questions / FAQ
Who is io.github.codespar/mcp-coordinadora for?
Solo builders and small teams shipping physical goods in Colombia who want agent help integrating Coordinadora APIs.
When should I use io.github.codespar/mcp-coordinadora?
While building checkout, label, or tracking features that must call Coordinadora in production, not during abstract market research.
How do I add io.github.codespar/mcp-coordinadora to my agent?
Add @codespar/mcp-coordinadora with stdio transport and set COORDINADORA_API_KEY and COORDINADORA_NIT in your MCP environment.