AIエージェントを通じて、静的ウェブサイト、ランディングページ、プロトタイプを即座にデプロイします。
別名 shipstatic/mcp, mcp, @shipstatic/mcp
- スター
- 6
- ツール
- 15
- ダウンロード数(30日間)
- —
- 最新バージョン
- 2.8.3
- 最終コミット
- 2026年11月12日
- ライセンス
- MIT
ShipStatic MCPとは
AIエージェントを通じて、静的ウェブサイト、ランディングページ、プロトタイプを即座にデプロイします。 15個のツールを提供しており、deployments_upload, deployments_list, deployments_getなどがあります。
プロジェクトのREADMEから生成された概要
ShipStatic MCP server について
ShipStaticを使用すると、開発者はAIエージェントを通じて静的ウェブサイト、ランディングページ、プロトタイプをデプロイできます。ホストされたURLを介したリモートサービスとして、またはSHIP_TOKENを使用したローカルプロセスとして機能します。ユーザーは、Claude Desktop、Cursor、Claude Code、VS Codeを含むさまざまなクライアントに接続できます。このMCP serverは、デプロイのライフサイクル全体を管理するための15個のツールを提供します。
アカウントを持っていないユーザーの場合、deployments_uploadツールを使用して、ファイルをライブURLに即座に公開できます。これらの匿名サイトは、クレームリンクが使用されない限り3日間アクティブなままです。登録ユーザーは、カスタムドメインの管理、すべてのデプロイ一覧の表示、自動クリーンアップのための特定の有効期限(TTL)の設定などの高度な機能を利用できます。また、特定のデプロイを訪問者から非公開にするためのパスワード保護もサポートしています。
できること
- 1プロトタイプの即時デプロイ現在のファイルをすぐにオンラインに公開するよう、AIエージェントに依頼してください。
- 2安全なプライベートプレビュー訪問者向けのパスワード保護機能を組み込んだ状態でサイトを公開するよう、エージェントにリクエストしてください。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
ShipStatic MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにShipStatic MCPをインストール
$ claude mcp add mcp -- npx -y @shipstatic/mcpCursorにShipStatic MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}VS CodeにShipStatic MCPをインストール
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}VS Code CLIにShipStatic MCPをインストール
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@shipstatic/mcp"]}'Claude DesktopにShipStatic MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}CodexにShipStatic MCPをインストール
$ codex mcp add mcp -- npx -y @shipstatic/mcpCodex config.tomlにShipStatic MCPをインストール
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@shipstatic/mcp"]
Gemini CLIにShipStatic MCPをインストール
$ gemini mcp add -s user mcp npx -- -y @shipstatic/mcpGemini settings.jsonにShipStatic MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
]
}
}
}HostedMCP が 2026年11月16日 に起動を確認
@shipstatic/mcp 2.8.3 をネットワークもキーもない隔離コンテナでこのコマンドで起動しました。応答があり、15個のツールが一覧表示されました。
ShipStatic MCPツール 15
tools/list でサーバーから取得deployments_uploadアクションDeploy a static site to a live URL: free, no account or API key required. **File content is plain text by default.** Pass HTML/CSS/JS/JSON/SVG/etc. directly in each file's `content` as a regular string. Only set `encoding: "base64"` per-file for binary content (images, fonts) — do not base64-encode text. Returns the live URL. Without a connected account, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private.
deployments_list読み取り専用List all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
deployments_get読み取り専用Get deployment details including URL, status, file count, size, labels, and password protection state.
deployments_setアクションUpdate deployment labels. Replaces all existing labels.
deployments_deleteアクションPermanently deletes a deployment and its files.
domains_setアクションCreate or update a domain: a ShipStatic domain (e.g. "yourname.shipstatic.com"), live as soon as a deployment is linked, or a custom domain (e.g. "www.example.com"), which needs DNS records first. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. For a custom domain, domains_records then returns the DNS records to configure.
domains_list読み取り専用List all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
domains_get読み取り専用Get domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`).
domains_records読み取り専用Returns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure.
domains_dns読み取り専用Returns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate.
domains_share読み取り専用Returns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share.
domains_validate読み取り専用Check if a domain name is valid and available before creating it. Returns the normalized form and availability.
| deployments_upload | Deploy a static site to a live URL: free, no account or API key required. **File content is plain text by default.** Pass HTML/CSS/JS/JSON/SVG/etc. directly in each file's `content` as a regular string. Only set `encoding: "base64"` per-file for binary content (images, fonts) — do not base64-encode text. Returns the live URL. Without a connected account, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private. | アクション |
| deployments_list | List all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next. | 読み取り専用 |
| deployments_get | Get deployment details including URL, status, file count, size, labels, and password protection state. | 読み取り専用 |
| deployments_set | Update deployment labels. Replaces all existing labels. | アクション |
| deployments_delete | Permanently deletes a deployment and its files. | アクション |
| domains_set | Create or update a domain: a ShipStatic domain (e.g. "yourname.shipstatic.com"), live as soon as a deployment is linked, or a custom domain (e.g. "www.example.com"), which needs DNS records first. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. For a custom domain, domains_records then returns the DNS records to configure. | アクション |
| domains_list | List all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next. | 読み取り専用 |
| domains_get | Get domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`). | 読み取り専用 |
| domains_records | Returns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure. | 読み取り専用 |
| domains_dns | Returns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate. | 読み取り専用 |
| domains_share | Returns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share. | 読み取り専用 |
| domains_validate | Check if a domain name is valid and available before creating it. Returns the normalized form and availability. | 読み取り専用 |
15個のツールをすべて表示ツールを折りたたむ
domains_verifyアクションTrigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Custom domains only, and refused once the domain is verified: read domains_get instead. Verification is asynchronous: read the domain again with domains_get to learn the verdict, since its `status` has not moved yet when this returns. A verified domain serves nothing until a deployment is linked with domains_set.
domains_deleteアクションPermanently deletes a domain.
whoami読み取り専用Returns your email and name, and the account's plan, usage and caps.
| domains_verify | Trigger DNS verification for a custom domain. Call after the user has configured DNS records from domains_records. Custom domains only, and refused once the domain is verified: read domains_get instead. Verification is asynchronous: read the domain again with domains_get to learn the verdict, since its `status` has not moved yet when this returns. A verified domain serves nothing until a deployment is linked with domains_set. | アクション |
| domains_delete | Permanently deletes a domain. | アクション |
| whoami | Returns your email and name, and the account's plan, usage and caps. | 読み取り専用 |
設定
SHIP_TOKEN
| 名前 | 説明 | 種類 |
|---|---|---|
| SHIP_TOKEN | — |
自動チェック
実行日 2026年11月16日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能shipstatic/mcp is public and reachablegithub.com/shipstatic/mcp ↗合格
- パッケージがこのリポジトリをソースとして指定@shipstatic/mcp names shipstatic/mcp as sourcenpmjs.com/package/@shipstatic/mcp ↗合格
- ビルドの来歴 (Sigstore 証明)Sigstore attestation for @shipstatic/mcpnpmjs.com/package/@shipstatic/mcp/v/2.8.3#provenance ↗合格
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-12github.com/shipstatic/mcp ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していないNo popular package one edit away from @shipstatic/mcp合格
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない15 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされているNo tool named like delete, drop or exec合格
- リモートエンドポイントが MCP ハンドシェイクに応答initialize answered with protocol 2025-11-25 in 218 ms; tools/list returned 15 tools合格
README
GitHubで見るShipStatic MCP
One URL. Your agent ships.
Deploy static websites, landing pages, and prototypes instantly. Free, no account needed.
Ask your agent to put your site online, and get back a real link you can share in seconds.
Try it in seconds, no account needed
Drop https://mcp.shipstatic.com into any MCP client. No install, no signup, no API key: your agent can publish a website in its next message.
https://mcp.shipstatic.com
ChatGPT
Add the ShipStatic plugin from its page in ChatGPT. There is nothing to paste.
Claude Desktop and claude.ai
Settings → Connectors → Add custom connector, paste https://mcp.shipstatic.com, save.
Claude Code
claude mcp add --transport http shipstatic https://mcp.shipstatic.com
Cursor, Antigravity, Devin Desktop, n8n, Zed, and anywhere with mcp.json
{
"mcpServers": {
"shipstatic": {
"url": "https://mcp.shipstatic.com"
}
}
}
VS Code
Install ShipStatic for VS Code. The server is built in, with no config at all.
Then just ask
"Publish this with ShipStatic."
Your agent publishes it, and you get back a link you can share right away, and a claim link. The site stays up for 3 days, and opening the claim link keeps it for good.
Want the site private? Say "publish this with ShipStatic's built-in password protection". Visitors have to type the password before they see anything, and saying "built-in" keeps your agent from writing a password page of its own.
Keep your sites with a free account
Everything above works with no account. A free account keeps your sites for good, gives you a ShipStatic domain like yourname.shipstatic.com, and shows you everything you've published in one place. A custom domain like www.example.com needs a paid plan.
Connect one when your client offers to sign you in, and the same URL answers with the rest. There's nothing to install and no key to paste: your client starts the sign-in itself.
Tools
All fifteen tools are on both doors. What changes is not which tools exist, but which ones answer: deployments_upload is the one that needs no account, and the other fourteen answer once you have connected one (hosted) or set SHIP_TOKEN (local).
Publishing, with no account
| Tool | Description |
|---|---|
deployments_upload |
Publish files and get a live URL instantly, optionally protected by a password |
Deployments, with an account
| Tool | Description |
|---|---|
deployments_list |
List all deployments with their URLs, status, labels, and password protection state. Pages with limit and cursor |
deployments_get |
Get deployment details including URL, status, file count, size, labels, and password protection state |
deployments_set |
Update the labels on a deployment for organization and filtering |
deployments_delete |
Permanently delete a deployment and all its files |
Domains, with an account
| Tool | Description |
|---|---|
domains_set |
Connect a custom domain to your site, switch deployments, or update labels |
domains_list |
List all domains with their linked deployment and verification status. Pages with limit and cursor |
domains_get |
Get domain details including linked deployment, verification status, and labels |
domains_records |
Get the DNS records you need to configure at your DNS provider |
domains_dns |
The DNS provider recorded for a domain, if known (e.g. Cloudflare, Namecheap) |
domains_share |
Get a shareable link so someone else can see the required DNS records |
domains_validate |
Check if a domain name is valid and available before connecting it |
domains_verify |
Check if DNS is configured correctly after you set up the records |
domains_delete |
Permanently disconnect and delete a custom domain |
Account, with an account
| Tool | Description |
|---|---|
whoami |
Your email and name, and the account's plan, usage and caps |
Paging long lists
deployments_list and domains_list accept limit and cursor. Each response carries a cursor: pass it back to fetch the next page. A null cursor means you're on the last one.
Retrying a deploy safely
deployments_upload accepts an idempotencyKey. If a deploy times out you cannot tell "it never landed" from "it landed and the response was lost", and retrying without a key creates a second site. Send the same key on the retry and you get back the site the first try made, once it went live. A key works only within your account: an anonymous deploy ignores it, and a retry makes a new site.
Key the attempt, not the try: a run id, a commit sha, or a uuid generated before the first call. A key that changes on every retry does nothing.
Deployments that clean themselves up
deployments_upload accepts a ttl in seconds. The deployment expires when the time is up and the platform removes it. That's useful for previews and quick experiments you'd otherwise have to remember to delete.
{ "path": "/path/to/dist", "ttl": 3600 }
It needs an account (a connected account on the hosted endpoint, or SHIP_TOKEN locally): a deploy with no account already expires on the platform's schedule, so a ttl on one is refused rather than ignored. A deployment carrying a ttl cannot be linked to any domain: deploy without one when the site needs a domain.
Run it on your own machine
This package runs the same fifteen tools, reached the other way: as a local process instead of the hosted URL. Use it when your MCP client doesn't speak OAuth yet, or when you'd rather set a key once than sign in. To publish a folder from your own machine, use the ShipStatic CLI instead: it reads the files straight from disk.
It needs Node.js 20.19 or newer, and takes one setting, SHIP_TOKEN, whose value is your API key from my.shipstatic.com/api-key. Without it, the local server works like the hosted URL with no account connected.
claude mcp add shipstatic -e SHIP_TOKEN=ship-your-api-key -- npx -y @shipstatic/mcp
Any other client takes the same command and setting in its mcp.json:
{
"mcpServers": {
"shipstatic": {
"command": "npx",
"args": ["-y", "@shipstatic/mcp"],
"env": { "SHIP_TOKEN": "ship-your-api-key" }
}
}
}
The MCP Registry lists ShipStatic as com.shipstatic/mcp, with the hosted URL.
Also available
| Surface | Reach it |
|---|---|
| CLI and SDK | npx @shipstatic/ship ./dist |
| VS Code | Search "ShipStatic" in the Marketplace |
| Plugin | Install it in Cursor, Claude Code, Codex or Gemini CLI |
| OpenCode | opencode plugin add opencode-shipstatic |
| n8n | Search "ShipStatic" in n8n's node panel |
| GitHub Action | shipstatic/action@v3 |
| Agent Skill | npx skills add shipstatic/plugin |
License
MIT
ShipStatic MCPのよくある質問
ShipStatic MCPをClaude Codeに追加するには
ターミナルでclaude mcp add mcp -- npx -y @shipstatic/mcpを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
ShipStatic MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
ShipStatic MCPが提供するツールは
15個のツールを提供しており、deployments_upload, deployments_list, deployments_get, deployments_set, deployments_deleteなどがあります。
匿名でのデプロイはどのくらいの期間オンラインですか?
アカウントなしで公開されたサイトは3日間保持されますが、提供されるクレームリンクを使用することで永続的に保持できます。
公開したサイトにパスワード保護をかけることはできますか?
はい、エージェントを通じてパスワード保護をリクエストできます。これにより、訪問者がサイトを閲覧する前にパスワードの入力を求めることができます。
カスタムドメインを使用するにはどうすればよいですか?
カスタムドメインには有料プランが必要ですが、無料アカウントではShipStaticドメインが割り当てられます。