Schema | Snaphost MCP

Snaphost MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`SNAPHOST_API_KEY`	Yes	Your Snaphost API key (looks like sk_...). Mint one in the dashboard under API keys.
`SNAPHOST_API_URL`	No	The Snaphost API base URL.	https://api.snaphost.ru

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
snaphost_deployA	Deploy a local project folder to Snaphost. Packs the folder (respecting .gitignore/.snaphostignore, dropping node_modules/.git/.env), uploads it, starts the build, waits, and returns the public URL. Costs vibecoins. No Dockerfile is needed: if the project has none, the platform generates one automatically — do NOT create a Dockerfile before deploying. If the project ships its own Dockerfile, the server inside it MUST listen on the PORT environment variable, otherwise the deployed URL will not respond.
snaphost_statusA	Get the status (and URL when running) of a Snaphost deploy.
snaphost_logsA	Fetch build/runtime logs for a Snaphost deploy. Pass next_since from a previous call to page.
snaphost_listC	List recent Snaphost deploys for the authenticated user.
snaphost_deleteB	Stop and delete a Snaphost deploy (frees its URL).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/justaba/snaphost-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server