Перейти до основного вмісту

Baltix MCP

Let your AI (Claude, Codex, Cursor, Claude Desktop) look up pickup points, check orders, and — if you allow it — create labels. You approve the connection in Baltix. You never copy a secret.

Paste this into your AI:

Set up the Baltix MCP for me: https://baltix-pickup-points.com/doc/mcp

A paid Baltix plan (Starter or higher) is required.


For you (the merchant)​

You do not need to create a token or edit config files. Your AI adds Baltix, then a browser window opens.

  1. Enter your shop (for example mystore or mystore.myshopify.com).
  2. You land in Shopify Admin → Baltix → Settings → MCP.
  3. Check what the AI may do:
    • Read is already on (search pickup points, see orders and labels).
    • Write is off. Turn it on only if you want the AI to change a pickup point or create/cancel a label.
  4. Click Allow, then Continue. Stay on this screen until Continue — that sends the AI back.

To disconnect later, open Settings → MCP and revoke the connection.

Baltix MCP is logistics only. It cannot change your billing, carrier passwords, or Shopify products.


For the AI (setup)​

Follow this section exactly. Do not ask the merchant to create or paste a token.

  1. Add the HTTP URL only. No Authorization header, no env var, no baltix_mcp_….
  2. Ask them to finish the browser steps above (shop → Allow → Continue).
  3. After Continue, call tools/list. Then read resource baltix://docs/mcp (or fetch https://app.baltix-pickup-points.com/mcp.llms.md).

Index for agents: https://app.baltix-pickup-points.com/llms.txt
Full dump (Cursor / Context7 / RAG): https://app.baltix-pickup-points.com/llms-full.txt

Endpoint: https://app.baltix-pickup-points.com/mcp

Do not use a warehouse API key (baltix_live_…) here. Do not call /api/v1 with this connection. Do not call Shopify Admin GraphQL through Baltix.

Claude Code​

claude mcp add --transport http baltix https://app.baltix-pickup-points.com/mcp

Codex​

In ~/.codex/config.toml or .codex/config.toml:

[mcp_servers.baltix]
url = "https://app.baltix-pickup-points.com/mcp"

Do not set bearer_token_env_var. If an old connect used a token: codex mcp logout baltix, then reconnect.

Cursor​

{
"mcpServers": {
"baltix": {
"url": "https://app.baltix-pickup-points.com/mcp"
}
}
}

No headers.

Claude Desktop​

Same JSON as Cursor (url only). If this build cannot open a browser, still do not put a secret in chat.

Tools​

Always available: search_docs — search official Baltix setup/FAQ docs. Use this before guessing how-to answers.

Read (on by default): search_pickup_points, list_orders, get_order, list_order_packages, list_order_labels, get_label, list_returns, get_return, list_return_dropoff_points, list_carrier_connections, get_tracking, preview_checkout_rates.

Write (only if they enabled it in Allow): change_order_pickup_point, create_pickup_change_link, replace_order_packages, create_order_label, create_package_label, cancel_label, create_return.

If a write tool is missing, ask them to reconnect and turn that write group on. Do not use the REST API instead.

Confirm with the merchant before any write. preview_checkout_rates is a Baltix preview, not a live Shopify callback. Carrier credentials stay hidden.

If something fails​

  • Browser did not open — re-add the MCP with the URL only.
  • They never see Allow — Baltix must be installed, paid plan, shop domain correct.
  • 401 — they did not finish Allow/Continue, or a warehouse key was sent. Reconnect. Do not ask for a token in chat.
  • 403 paid_plan_required — Free plan.
  • 403 insufficient_scope — reconnect and enable write in Allow.
  • 429 — slow down (about 120 requests/min).