Connect Your Coding Agent to Shipfox (MCP)

Connect Claude Code, Codex CLI, Cursor, VS Code, OpenCode, Zed, or Antigravity to the Shipfox MCP server. Verify or disconnect the app in Shipfox.

Connect an existing coding agent to the Shipfox MCP server. The agent gets access to one workspace. It can read workspace data, download step logs, and start or manage workflow runs. Your browser handles sign-in. For server details and the tool list, see the reference for the Shipfox MCP server.

Add the Shipfox MCP server to your client

Self-hosted installations use their own endpoint instead of https://api.shipfox.io/mcp. Copy it from Settings → Shipfox MCP server.

https://api.shipfox.io/mcp

Run this command in your terminal:

claude mcp add --transport http shipfox https://api.shipfox.io/mcp

Open Claude Code and run /mcp. Select shipfox and complete the browser sign-in.

Claude Code reads the server's skill and docs resources on its own.

Approve access in Shipfox

Your client opens Shipfox in the browser. Choose the workspace the agent may use, then select Allow access. Select Deny if the app name doesn't match the client you started.

Verify the connected app

Ask the agent to list the Shipfox projects. It calls list_projects and returns projects from the workspace you chose.

In Shipfox, open Shipfox MCP server under Settings. The app appears under Connected apps with the date when Shipfox connected it.

Review connected apps

Connected apps lists every app for the current workspace. Each row shows two dates: when Shipfox connected the app and when the app last refreshed access.

Shipfox stops refreshing access when:

You leave the workspace.
Shipfox suspends the workspace.
Shipfox suspends your account.
30 days after you connect. Connecting again restarts the 30 days.

The next refresh fails. The client asks you to connect again.

Disconnect an app

Select Disconnect on the app's row. Confirm Disconnect app. The app can no longer start or manage workflow runs or download logs. Read access can continue for up to 15 minutes.

Disconnecting does not remove the server from your client. Remove the server entry if you no longer need it. Otherwise, the client asks you to sign in again.

Switch to another workspace

A client stores one Shipfox sign-in for each endpoint. That sign-in uses one workspace. Clear it before connecting the client to another workspace. In Claude Code, select Clear authentication in the /mcp menu. Connect again and choose another workspace. Disconnect the old app in Shipfox when you no longer need it.

The browser did not open. Copy the sign-in URL from the client output. Open the URL in your browser.
The request expired. Start again from the client. See Access lifetime.
Shipfox rejected the callback. Shipfox accepts HTTPS and localhost callback URLs only. Use one of the clients above, or update your client.
A self-hosted endpoint does not respond. Ask your administrator to check that the API's public URL is reachable through HTTPS.
Tool calls fail with rate-limited. The agent reached the tool call limit. See Limits.

Was this page helpful?

Edit this page on GitHub