Open Agents in your workspace, choose your app, and follow the three steps. This page has the same steps for each client. The Agents page shows the server URL of this deployment. This page uses the hosted URL https://mcp.shipcontent.com/mcp. On a local server, use http://localhost:3000/mcp instead (Connect local). The client guides follow the official documentation of each client. They are not a claim that each client passed an end-to-end ShipContent test.
Three steps#
- Add ShipContent. Use the setup for your client below. Every client uses the same server URL: the hosted URL
https://mcp.shipcontent.com/mcp, or the URL the Agents page shows. - Sign in and approve. Your app opens ShipContent sign-in. If ShipContent asks you to choose a plan, select Free or complete Pro payment first. Return to the same connection request, then select Allow once for all your workspaces, including new ones. The app stays connected until you disconnect it. Publish is optional: select its box and type
allow agent. Updated 2026-11-07: you can also do this later with Allow in the agent's Publish social posts row on the Agents page. On the Agents page, the status line shows Connected when the new access is saved. Check connection looks for new access for up to ten minutes. - Test it. Copy the first prompt from the Agents page and send it in a new conversation. The prompt names your workspace and its workspace UUID. It only reads: it calls
get_onboarding_statusand does not create or publish anything.
When an agent is connected, the Agents page lists it first. Connect another agent opens the same steps.
Claude Code#
Run this command in your terminal. It adds ShipContent and starts Claude Code.
claude mcp add --transport http --scope user shipcontent 'https://mcp.shipcontent.com/mcp' && claude
In Claude Code, run /mcp, select shipcontent and choose Authenticate. Your browser opens ShipContent sign-in. Select Allow for your account. Then send the first prompt from the Agents page.
Claude Code loads servers only when it starts. Exit any open Claude Code session before you run the command. If you add the server in an open session, /mcp does not show it until you start Claude Code again. See the Claude Code setup guide.
Codex#
Run these commands in your terminal:
codex mcp add shipcontent --url 'https://mcp.shipcontent.com/mcp'
codex mcp login shipcontent
The Codex app, CLI and IDE extension share this setting. See the Codex setup guide.
Cursor#
Select Add to Cursor on the Agents page, or add this JSON to ~/.cursor/mcp.json:
{
"mcpServers": {
"shipcontent": {
"url": "https://mcp.shipcontent.com/mcp"
}
}
}
Keep any servers that are already in your mcpServers object. Enable ShipContent in Cursor and follow its sign-in prompt. See the Cursor setup guide.
VS Code#
Select Add to VS Code on the Agents page, or add this JSON to .vscode/mcp.json:
{
"servers": {
"shipcontent": {
"type": "http",
"url": "https://mcp.shipcontent.com/mcp"
}
}
}
Start the server and follow its sign-in prompt. See the VS Code setup guide.
Claude#
In Claude, open Customize → Connectors and select + Add → Add custom connector. Name it ShipContent, paste https://mcp.shipcontent.com/mcp, then select Connect. A team owner may need to add the connector first. The Agents page has an Open Claude link to the connector settings. See the Claude setup guide.
ChatGPT#
In ChatGPT, open Plugins and select + → Create custom MCP server. Name it ShipContent, paste https://mcp.shipcontent.com/mcp, choose OAuth, then create and install the plugin. Your ChatGPT account or workspace must allow custom MCP servers.
After you install the plugin, start a new conversation. Type @ and select ShipContent before you send the first prompt. The Agents page has an Open ChatGPT link to the plugin settings. See the ChatGPT setup guide.
Other clients#
Add a remote MCP server named ShipContent with the URL https://mcp.shipcontent.com/mcp. Choose Streamable HTTP and OAuth when the client asks. The client must support Streamable HTTP and OAuth. A model API key alone does not connect it.
Trouble connecting#
- No ShipContent tools? Enable the server and start a new conversation.
- Wrong or missing workspace? Call
list_workspacesand check the signed-in owner. One connection includes all workspaces of that owner.
To connect to a local app, see Run MCP locally.