ship-page
One-call static page/site deploys for AI agents — POST HTML, a files map, or a zip and get back a live unguessable URL. Remote endpoint at https://ship.page/mcp, free tier needs no account or API key.
README
ship.page MCP server
Throw HTML at an API, get back a live URL. ship.page is a remote MCP server + plain REST API that lets an AI agent put content on the public internet — no account, no API key, no OAuth dance. One POST, one live *.shipped.page URL.
Endpoint
https://ship.page/mcp
Client config:
{
"mcpServers": {
"ship.page": { "url": "https://ship.page/mcp" }
}
}
Transport: Streamable HTTP. No auth required for anonymous deploys (7-day retention). Pass Authorization: Bearer sp_… (free key from the dashboard) for 30-day drops and higher limits; Pro drops never expire.
Tools
| Tool | What it does |
|---|---|
deploy_html |
Deploy a single HTML page, returns a live URL |
deploy_files |
Deploy a multi-file site from a path → content map (base64 for binaries) |
append_files |
Add files to an existing owned drop |
list_drops |
List the authenticated account's drops |
claim_drop |
Claim an anonymous drop into an account (slug + claim token) |
restore_drop |
Restore an expired drop (free ≤30d past expiry, paid ≤90d) |
delete_drop |
Delete an owned drop |
get_limits |
Plan matrix, quotas, and current usage |
get_account |
Account + plan status for the current key |
Errors come back as structured JSON with a human-readable hint agents can relay verbatim when something is plan-gated.
Local / stdio clients
For clients that only speak stdio, bridge via mcp-remote:
{
"mcpServers": {
"ship.page": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ship.page/mcp"]
}
}
}
The included Dockerfile packages exactly this bridge, so the server can be built and introspected as a standard container (e.g. by directory scanners).
REST API
Everything the MCP tools do is also plain HTTP. Full OpenAPI 3.1 spec: ship.page/openapi.json
curl -X POST https://ship.page/deploy \
-H "Content-Type: text/html" \
--data-binary @report.html
Links
- Docs: ship.page/docs/agents
- GitHub Action: bitgate/ship-page-action
- Glama connector: glama.ai/mcp/connectors/page.ship/ship-page
- Official MCP registry:
page.ship/ship-page
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.