Can I use ShipBob as a CLI?

Yes. KosmoKrator exposes a ShipBob CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose ShipBob through MCP?

Yes. The KosmoKrator MCP gateway can expose selected ShipBob tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are ShipBob credentials stored?

ShipBob credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for ShipBob MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

ecommerce

ShipBob MCP Integration for Codex

Connect ShipBob to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit ShipBob feedback View package source

Connect ShipBob to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

ShipBob MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-shipbob": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=shipbob",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=shipbob --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only ShipBob instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

ShipBob Tools Visible to Codex

Codex sees stable MCP tool names generated from the ShipBob integration catalog.

MCP tool	Source function	Type	Description
`integration__shipbob__shipbob_list_orders`	`shipbob.shipbob_list_orders`	Read	List fulfillment orders from ShipBob. Supports pagination and filtering by status (e.g. pending, fulfilled, cancelled).
`integration__shipbob__shipbob_get_order`	`shipbob.shipbob_get_order`	Read	Get details for a specific ShipBob order by ID, including line items, shipping address, and fulfillment status.
`integration__shipbob__shipbob_create_order`	`shipbob.shipbob_create_order`	Write	Create a new fulfillment order in ShipBob. Provide product line items, a receiving note, and an optional shipping method.
`integration__shipbob__shipbob_list_products`	`shipbob.shipbob_list_products`	Read	List products in your ShipBob inventory. Supports pagination with page and limit parameters.
`integration__shipbob__shipbob_get_product`	`shipbob.shipbob_get_product`	Read	Get details for a specific ShipBob product by ID, including SKU, inventory levels, and fulfillment info.
`integration__shipbob__shipbob_list_shipments`	`shipbob.shipbob_list_shipments`	Read	List shipments from ShipBob. Supports pagination with page and limit parameters.
`integration__shipbob__shipbob_get_current_user`	`shipbob.shipbob_get_current_user`	Read	Get the currently authenticated ShipBob user profile. Useful for verifying connectivity and account details.

Related ShipBob Pages

ShipBob CLIUse direct JSON commands instead of MCP discovery. ShipBob MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.