Build in Gemini CLI.
Publish on Shipvela.

Connect your account

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

gemini extensions install https://github.com/stefanautomateed/shipvela-codex

1. Review the extension configuration and enable Shipvela in a trusted project.
2. Start Gemini CLI and run /mcp auth shipvela. Complete Shipvela OAuth in your browser.
3. Use /shipvela:publish or ask Gemini to publish your website. Review the intended target before publishing.

Requires Gemini CLI with extension and remote OAuth support. For manual setup, merge this configuration into .gemini/settings.json. Keep tool confirmations enabled. Install and authenticate Gemini itself separately through Google's normal flow.

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": {
      "httpUrl": "https://shipvela.com/mcp",
      "timeout": 60000,
      "trust": false,
      "oauth": {
        "enabled": true,
        "issuer": "https://shipvela.com"
      }
    }
  }
}

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.