Summary
The deploy call is the whole product here; search_project and view_project_detail exist to find what it created.
deploy_site returns the domain URLs alongside the deployment detail, so an agent that deploys already knows where the site landed without a follow-up. Passing project_id against project_name is the only branch in the interface, and it decides whether this is an update or a new project. search_project and view_project_detail are how a later session picks the thread back up, since nothing here walks the full project list.
What it is
A 4EVERLAND Hosting client with three tools: deploy a site's files to a project and receive the deployment detail, search projects by keyword, and read one project's detail by id.
What you get
- deploy_site takes the code files and a platform with either an existing project_id or a project_name, and returns the deployment detail including the domain URLs.
- search_project finds projects by keyword.
- view_project_detail returns one project's detail by id.
Requirements
A 4EVERLAND account and its token, supplied as TOKEN.
Setup effort
One command plus a key — npx -y @4everland/hosting-mcp@latest serve, then supply credentials