Snaphost MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Snaphost MCPdeploy this project to Snaphost and give me the URL"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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/mcpOr skip the install and let your agent run it through npx (see below).
Related MCP server: CreateOS MCP
Setup
Mint an API key in the Snaphost dashboard under API keys, or
POST /api/v1/keys. It is shown once and looks likesk_....Register the server with your agent.
Claude Code:
claude mcp add snaphost \ --env SNAPHOST_API_KEY=sk_... \ -- npx -y @snaphost/mcpCursor (
.cursor/mcp.json) — or any client using the same format:{ "mcpServers": { "snaphost": { "command": "npx", "args": ["-y", "@snaphost/mcp"], "env": { "SNAPHOST_API_KEY": "sk_..." } } } }Tell the agent to deploy: "deploy this project to Snaphost".
Environment
Variable | Required | Default |
| yes | — |
| no |
|
Tools
Tool | What it does |
| Pack the folder, upload, build, wait, return the public URL. |
| Deploy status; URL when running. |
| Build/runtime logs (paged via |
| Recent deploys. |
| 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 venvSymlinks 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 typecheckRequires Node 20+.
License
MIT
Maintenance
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
- Flicense-qualityCmaintenanceDeploy, manage, and scale applications directly from your AI assistant.Last updated3
- Flicense-qualityBmaintenanceDeploy full-stack apps from AI. 75+ tools: GitHub/Docker deploy, databases, environments, security, billing.Last updated2
- AlicenseAqualityCmaintenanceEnables AI agents to deploy applications and manage servers over SSH using natural language commands, with built-in tools for Python bots, Docker Compose, and SSL setup.Last updated6MIT
- Alicense-qualityBmaintenanceEnables AI agents to deploy code to any hosting provider by creating PRs, building, and verifying health checks, all from a single natural language command.Last updatedMIT
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.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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