Labsco
MCP SERVER · OFFICIAL PROJECT

InstaPods

by instapods ↗

Create a pod, push your code to it, and have the URL checked from outside before anyone says it is live.

PaaS Deployment & App Hosting✓ Official source
Summary
The deploy is one call, and it tells you when the URL is not really serving.

A single tool takes code from the assistant to a live HTTPS URL, then checks the URL from outside the container and reports public: false with a reason when a visitor would see nothing. A pod that exists, runs, and serves no one is the failure this catches.

What it is

InstaPods' hosted MCP server for its container hosting. The client connects to one endpoint, authorizes against a team, and gets 18 tools covering pods, 1-Click Apps, files, commands, logs and visitor feedback.

What you get
  • Pods listed and filtered by name, status or preset, opened in detail, created, started, stopped, restarted, reloaded, deleted, and moved between the launch, build, grow, scale and turbo plans
  • One call that does the whole deploy — creates the pod if it is missing, uploads the files, installs dependencies, restarts the app, and reports whether an outside visitor's request to the URL actually succeeded
  • Ready-to-run applications from the 1-Click catalog deployed by slug — n8n, Uptime Kuma, Vaultwarden and the rest boot working, with nothing uploaded
  • Files on a pod listed, read and written, and shell commands run as the instapod user
  • Logs from journalctl, either the tail or a regex search across the whole journal, filtered by service
  • The visitor feedback widget switched on, scoped to everyone or to a share link, and comments triaged one by one
  • The catalog itself readable — apps, presets, plans and regions — so a choice is made rather than guessed
  • Every tool declares an outputSchema, so a client knows the shape of a result before it calls
Requirements

An InstaPods account and a client that speaks remote MCP. The server is reached over streamable HTTP at https://app.instapods.com/api/mcp; the client registers itself and completes an OAuth 2.0 exchange with PKCE, you sign in and pick which team it gets, and the token lasts 30 days. Billing stays on the InstaPods dashboard — no tool here asks for card details — and a first custom-code deploy with no card on file can be granted a trial pod on the launch plan that is deleted after 90 minutes unless you keep it.

Setup effort

One command — npx -y mcp-remote https://app.instapods.com/api/mcp