Skip to content

Connect with the ShipContent plugin

Implemented

Install the ShipContent plugin, connect your account once with OAuth, and use the current Publish permission across your workspaces.

Connect ShipContent to draft posts, prepare media proposals and manage channels from ChatGPT or Codex. One OAuth connection covers every current and future workspace of the owner. The public directory package is still a draft; it is not published.

Test a local package#

Add this checkout as a Codex marketplace:

sh
codex plugin marketplace add .

Refresh the Plugins Directory in the desktop app, select ShipContent local, and install ShipContent. Open its connection flow and sign in. The package uses https://mcp.shipcontent.com/mcp; its server name is shipcontent-plugin.

Package 0.1.5 declares OAuth with CIMD registration and the offline_access base scope. The server advertises mcp:access as its resource scope. Refresh access needs both scopes. Installation alone does not prove a working connection. If the client cannot connect a local package, use the hosted connection steps.

Test in ChatGPT#

In Developer Mode, add a custom MCP server with https://mcp.shipcontent.com/mcp and OAuth. For a manual connection, set the base scope to offline_access and keep the resource scope mcp:access. A connection with only mcp:access cannot renew after its short access-token lifetime. Check that your ChatGPT plan can run the plugin before testing workflow calls.

Call list_workspaces and follow its cursor. Read access.canPublish, then use a returned workspaceId with get_onboarding_status. Select the workspace for each later call. A browser session alone does not connect an agent. See hosted OAuth for registration and recovery.

Use the workflows#

The package includes draft-post, prepare-reel and connect-channels. Each workflow uses the selected workspace's own facts and saved media. Saved drafts, readiness, approval, queued work and delivery are separate states.

Account Publish permission permits direct MP4 uploads and supported publication or schedules for automatic posts. Owner-set review posts, generation spend and provider authorization still require owner actions. Never change an owner's review choice to automatic. When the server requires a plan or credits, return the owner billing handoff. Read get_credit_prices and get_credit_balance before preparing a paid media request. See billing and owner handoffs.

Submission status#

Package 0.1.5 is uploaded to the existing OpenAI draft. Publisher and domain verification are complete and OAuth is authorized. Check the portal for the current metadata, skill and MCP scan results before submission.

A dedicated reviewer account, five positive and three negative case runs, and an accessible walkthrough recording are still required. Prior owner-account checks do not complete reviewer acceptance. Credentials belong only in the portal's secure reviewer form. The support link opens the website, whose footer contains the support email.

See the OpenAI submission guide for review and publication.