Server facts
shipstatic mcp
Project
- Author
- shipstatic
- Repository
- github.com/shipstatic/mcp
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 6
- Last commit
- Data as of
Tags
- cdn
- cloud
- deploy
- hosting
- ship
- static hosting
Overview
Static-site publishing through ShipStatic starts with an AI agent uploading a build output directory. The upload returns a unique live address alongside the file count and size. Uploads made without credentials are public and expire after 3 days; their responses also provide a claim link that users can visit to retain the site permanently. A free API key makes deployments permanent and associates them with the user's account. Deployment tools also let agents browse existing uploads, inspect status and metadata, replace labels, and delete deployments and their files.
Custom-domain workflows cover reserving a name, linking it to a deployment, switching the linked deployment, and updating labels. Agents can check name validity and availability, retrieve required DNS records, identify the DNS provider, and obtain a shareable setup hash for viewing records without an API key. Once the user configures DNS, verification can be triggered asynchronously, with status changing as DNS propagates. Domain listing and detail tools expose deployment links and verification state, while account lookup reports email, plan, and usage. Deployment and domain deletion workflows require user confirmation.
shipstatic mcp setup notes
- shipstatic mcp records stdio only; confirm a network transport upstream before planning remote access.
- shipstatic mcp has no recorded license; confirm reuse terms in its repository.