ShippedConnect your agent
Connect Grok CLI
Configure Grok CLI to ship an app from your local workspace.
Prepare your connection
Complete “Set up the Shipped connector” first. You need the local connector, absolute paths, and a private SHIPPED_API_TOKEN environment variable.
This guide is for the Grok command-line coding agent. Grok’s web connectors need a remote MCP endpoint, which Shipped does not currently provide.
Add Shipped
Add this server entry to ~/.grok/config.toml. Merge it with your existing configuration so other servers stay available. Replace the sample paths with your own.
The example references your token’s environment variable. It contains no token value.
[mcp_servers.shipped]
command = "/absolute/path/to/node"
args = ["--import","/absolute/path/to/Shipped Platform/node_modules/tsx/dist/loader.mjs","/absolute/path/to/Shipped Platform/apps/mcp/src/index.ts"]
[mcp_servers.shipped.env]
SHIPPED_API_URL = "https://app.shippedit.io"
SHIPPED_WORKSPACE_ROOT = "/absolute/path/to/your/app"
SHIPPED_API_TOKEN = "${SHIPPED_API_TOKEN}"Check the tools
Run grok mcp doctor shipped to check the connection. In a Grok session, /mcps shows your servers.
Ask the agent to list your Shipped projects. Confirm the workspace before giving it a deployment instruction.
List my Shipped projects, then help me plan this app’s deployment.Client configuration checked October 15, 2026. Official Grok CLI MCP documentation.