Build in Cline.
Publish on Shipvela.

Connect your account

First, create your Shipvela account and verify your email. Install the current official client, then add Shipvela:

cline mcp add shipvela https://shipvela.com/mcp --transport streamable-http

1. Review the MCP add wizard. Keep automatic tool approval disabled for Shipvela.
2. Connect the Shipvela server through Cline's MCP settings and complete OAuth in the browser when prompted.
3. Ask Cline to publish your website. Inspect the target and public files, then track the exact deployment to its live URL.

Requires a current Cline client with Streamable HTTP and OAuth support. In the extension, merge the entry into cline_mcp_settings.json through MCP server settings. Configure your own model provider in Cline separately. This is a remote MCP integration; the Codex/Claude marketplace plugin format is not a Cline plugin.

Prefer configuration?

Merge the Shipvela entry into your existing MCP configuration. Preserve your other servers. The hosted endpoint uses Streamable HTTP with OAuth; no AWS or GitHub token belongs in this file.

{
  "mcpServers": {
    "shipvela": {
      "type": "streamableHttp",
      "url": "https://shipvela.com/mcp",
      "timeout": 60,
      "autoApprove": [],
      "disabled": false
    }
  }
}

Your first publish

“Publish this website on Shipvela. Confirm the target, use the appropriate publishing path, follow the exact deployment and give me the live URL.”

For a small built HTML/CSS/JS site, your assistant returns a review link. Open it, inspect the public files and click Confirm & publish. For a GitHub project, connect GitHub in Shipvela first and select your repository and production branch. Larger local builds use the separately authorized Shipvela CLI.

Publishing uses your plan allowance and may replace the selected website. A queued request is not a live deployment. Ask your assistant to check the exact job until it succeeds and return its HTTPS URL.

Access you control

Shipvela asks you to approve account access. Connections expire after 90 days unless revoked sooner. They cannot change billing, delete projects or read environment secrets. Revoke access in Settings.

Hobby includes 3 projects and 20 publishes per month. MCP chat uploads support 500 KB and 100 public files, including a root index.html. CLI uploads support 50 MB and 5,000 built files. Static React, Vite, Astro and HTML output are supported; GitHub Next.js static exports, including Next.js 16, work on Hobby. stable Next.js SSR 12+ requires GitHub and a paid plan. Databases and arbitrary backend servers are not provisioned.

Direct installation is available. Official marketplace approval and client subscription availability are separate.