Shipvela
Server Details
Create website projects, deploy GitHub sites and read logs/usage via remote OAuth MCP.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 37.3% over 25 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there are two clusters that require careful reading: create_project/deploy_project/prepare_static_publish all touch creation/publishing, and get_deployment/get_operation/get_build_logs all read status. The descriptions do a good job of clarifying the boundaries (e.g. operation success vs provider deployment completion), keeping misselection low.
All 11 tools follow a consistent snake_case verb_noun pattern (create_project, deploy_project, detect_framework, get_*, list_*, prepare_static_publish). No mixed conventions or vague standalone verbs.
11 tools is well-scoped for a deployment/hosting platform, covering project creation, deployment, static publishing, diagnostics, and account usage. Each tool earns its place with no obvious redundancy.
Creation, listing, reading, and publishing are covered, but there is no update_project or delete_project, and no explicit domain/teardown operations, leaving lifecycle gaps (create+get+list but no update/delete). Agents may hit dead ends for project modification or cleanup.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
create_project1 field changed- changed
Input schema / properties / project / properties / framework / enumPrevious value: -[ - "vite", - "next", - "static" -]New value: +[ + "vite", + "next", + "next-static", + "static" +]
1 tool update
- Added
prepare_static_publish
10 tool updates
- First observed
create_project - First observed
deploy_project - First observed
detect_framework - First observed
get_build_logs - First observed
get_deployment - First observed
get_operation - First observed
get_project - First observed
get_usage - First observed
list_projects - First observed
list_repositories
Related MCP Connectors
Manage existing DotMoose hosting services through OAuth-protected MCP tools.
Agent-first web hosting: deploy sites, apps, databases and domains over MCP.
Manage Aderlo Cloud hosting: files, DNS, MySQL/PostgreSQL databases and WP-CLI over OAuth scopes.
Build, deploy, and host full-stack web apps from any MCP client. DB, auth, storage, cron included.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceDeploy GitHub repositories or local directories to private URLs directly from an MCP client. Includes tools for managing deployments, reading build logs, and stopping services.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to deploy and manage compatible web apps, isolated Postgres databases, and project file storage, while inspecting build logs, runtime errors, and usage through an OAuth-authenticated remote MCP connection.MIT
- AlicenseAqualityBmaintenanceMCP server for publishing HTML or Markdown to a live hosted URL via htmldrop. Provides tools to publish, list, and delete hosted sites, with remote OAuth and API token authentication.322 npmMIT
- AlicenseAqualityCmaintenanceDeploys and manages projects on Swigs Cloud from any MCP client, turning folders or git repositories into live HTTPS sites in about two minutes.812 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.