Skip to main content
Glama

Snaphost MCP server

Deploy the project you are working on straight from your AI agent (Claude Code, Cursor, any MCP client) and get a public URL back.

No Dockerfile required: if the project does not ship one, Snaphost generates it. The folder is packed locally, uploaded, built, and run — the agent gets back a URL it can hand you.

Install

npm install -g @snaphost/mcp

Or skip the install and let your agent run it through npx (see below).

Related MCP server: CreateOS MCP

Setup

  1. Mint an API key in the Snaphost dashboard under API keys, or POST /api/v1/keys. It is shown once and looks like sk_....

  2. Register the server with your agent.

    Claude Code:

    claude mcp add snaphost \
      --env SNAPHOST_API_KEY=sk_... \
      -- npx -y @snaphost/mcp

    Cursor (.cursor/mcp.json) — or any client using the same format:

    {
      "mcpServers": {
        "snaphost": {
          "command": "npx",
          "args": ["-y", "@snaphost/mcp"],
          "env": { "SNAPHOST_API_KEY": "sk_..." }
        }
      }
    }
  3. Tell the agent to deploy: "deploy this project to Snaphost".

Environment

Variable

Required

Default

SNAPHOST_API_KEY

yes

SNAPHOST_API_URL

no

https://api.snaphost.ru

Tools

Tool

What it does

snaphost_deploy

Pack the folder, upload, build, wait, return the public URL.

snaphost_status

Deploy status; URL when running.

snaphost_logs

Build/runtime logs (paged via next_since).

snaphost_list

Recent deploys.

snaphost_delete

Stop and delete a deploy.

What gets uploaded

snaphost_deploy packs the folder into a tar.gz in memory, honouring .gitignore and .snaphostignore. These are dropped unconditionally, whatever the ignore files say:

.git  node_modules  .env  .env.*  *.local.env  .DS_Store
dist  build  .next  .nuxt  coverage  __pycache__  *.pyc  .venv  venv

Symlinks are skipped — the server rejects them. The upload is capped at 50 MB compressed by default; the ignore rules keep a typical project far below that.

Add a .snaphostignore to exclude more. .env files never leave your machine, so anything the deployed app needs at runtime has to be configured on the platform side.

If the project ships its own Dockerfile

The runtime injects a PORT environment variable and invokes the container on it. A server hard-bound to a fixed port builds and deploys fine but never receives traffic. Make it listen on process.env.PORT (or the equivalent), falling back to a local default.

Development

npm install
npm run build     # tsc -> dist/
npm run typecheck

Requires Node 20+.

License

MIT

Install Server
A
license - permissive license
A
quality
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • Your AI builds, deploys, and runs full-stack apps on a hosted workspace created at first sign-in.

  • Agent-first hosting: create apps, commit code, deploy, get HTTPS URLs. OAuth sign-in, no tokens.

  • Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.

View all MCP Connectors

Latest Blog Posts

MCP directory API

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