# Shipvela [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://shipvela.com/integrations/codex  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/shipvela

## Description
Shipvela vendor-maintained remote Streamable HTTP MCP at https://shipvela.com/mcp for creating website projects, deploying supported GitHub repositories, and reading operation/deployment status, build logs and usage. Requires a Shipvela account with OAuth S256 PKCE and dynamic client registration; GitHub deployment uses an existing Shipvela GitHub connection. Hobby starts free with 3 projects and 20 publishes/month; paid plans are available. Public beta Codex plugin and publishing skill: https://github.com/stefanautomateed/shipvela-codex. Hosted runtime is private and no source license or authenticated health benchmark is claimed. Maker submission by Stefan Mitrovic with Codex assistance.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "shipvela": {
    "url": "https://shipvela.com/mcp"
  }
}
```

## Documentation

## What Shipvela MCP server does

Shipvela MCP server exposes Shipvela website project and publishing operations through a remote Streamable HTTP MCP endpoint at `https://shipvela.com/mcp`. Agents can create website projects, deploy supported repositories from GitHub, and inspect the state of operations and deployments. The available read-oriented information includes build logs and usage data.

GitHub deployment depends on an existing GitHub connection in the Shipvela account.

This listing belongs to the 💻 Developer Tools category and is relevant for agent workflows that need to create or publish Shipvela projects without implementing Shipvela’s service calls directly.

## How it works

Shipvela MCP server runs as a vendor-maintained remote service rather than a local process. MCP clients connect to the hosted Streamable HTTP endpoint, and authorization uses a Shipvela account with OAuth S256 PKCE and dynamic client registration. These requirements indicate that client setup includes an OAuth-based authorization flow rather than a static API key supplied through an environment variable.

After authorization, an agent can request project creation, repository deployment, or status and diagnostic information through MCP. Deployment operations use the GitHub connection already associated with the Shipvela account.

## Setup and configuration

Configure an MCP-compatible client to use `https://shipvela.com/mcp` as a remote Streamable HTTP server. A Shipvela account is required. During authorization, the client must support OAuth S256 PKCE and dynamic client registration, or provide an equivalent supported configuration flow.

For GitHub-based deployments, connect GitHub to Shipvela before asking an agent to deploy a repository. A public beta Codex plugin and publishing skill are available at `https://github.com/stefanautomateed/shipvela-codex`.

## Tools and capabilities

The documented capabilities include:

- Creating website projects.
- Deploying supported GitHub repositories.
- Reading operation status.
- Reading deployment status.
- Reading build logs.
- Reading usage information.

The exact MCP tool names and parameters are not provided. Confirm the exposed schema in the client after authorization before building automation around specific arguments or return values.

## Limitations and notes

Shipvela MCP server is described as a public beta integration for Codex, so behavior and client support may change. The hosted runtime is private, and no source license is claimed.

The service requires an account and OAuth authorization, and repository deployment requires an existing Shipvela GitHub connection. Pricing information states that the Hobby plan starts free with three projects and 20 publishes per month; paid plans are also available.

_Full upstream README: https://allmcps.com/mcp/shipvela/readme_

