InstaPods

com.instapodsPublished by instapods.comOfficial publisherv1.1.0Updated Oct 24, 2026

Deploy and manage web apps on InstaPods: create pods, push files, run commands, read logs.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

InstaPods MCP server lets an assistant deploy and manage web apps on InstaPods hosting: create pods, push files, run commands and read logs.

What you can do
  • Create and manage InstaPods app pods on hosted Linux servers
  • Push application files and deploy Node.js, Python, PHP or static apps
  • Run commands inside a pod and read logs for debugging
  • Use built-in guided prompts for deployment, pod diagnosis and getting started
When to use it
Useful when you want an assistant to deploy a web app to InstaPods hosting, debug a failing pod such as a 502 error, or add a database to a pod, without leaving the chat.
Requirements
Remote MCP endpoint at app.instapods.com over streamable HTTP; OAuth sign-in is required and prompted on first use. An InstaPods account is implied. No environment variables or headers are declared.
Before you install
The server can create pods, push files, run commands and change hosting state, so actions affect a live deployment. OAuth grants access to your InstaPods account. Review commands and deployments before approving them.

Installation

In SourceWeft

  1. Open InstaPods in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.instapods%2Finstapods/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "instapods": {
      "type": "http",
      "url": "https://app.instapods.com/api/mcp"
    }
  }
}

README

InstaPods SDK

Tools and integrations for deploying and managing apps on InstaPods with AI assistants.

InstaPods is app hosting for developers — real Linux servers, one command. Deploy Node.js, Python, PHP, and static apps in seconds. This SDK provides two ways to integrate InstaPods with Claude:

Integration Paths

Claude Code (CLI Skill)

A skill that teaches Claude Code how to deploy and debug apps using the instapods CLI.

Setup:

  1. Install the CLI:

    bash
    curl -fsSL https://instapods.com/install.sh | shinstapods auth login

  2. Copy the skill to your project:

    bash
    mkdir -p .claude/skills/instapods-clicurl -fsSL https://raw.githubusercontent.com/instapods/sdk/main/skills/instapods-cli/SKILL.md \  -o .claude/skills/instapods-cli/SKILL.md

  3. Ask Claude Code to deploy:

    > deploy my app to instapods> my app is returning 502, help me debug> add a PostgreSQL database to my pod

Claude Desktop / Claude.ai (MCP Skill)

Two options — use the MCP skill for guided workflows, or connect directly via MCP.

Option A: MCP Skill (recommended)

Copy the skill to your project:

bash
mkdir -p .claude/skills/instapods-mcpcurl -fsSL https://raw.githubusercontent.com/instapods/sdk/main/skills/instapods-mcp/SKILL.md \  -o .claude/skills/instapods-mcp/SKILL.md

Option B: Direct MCP connection

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

json
{  "mcpServers": {    "instapods": {      "url": "https://app.instapods.com/api/mcp"    }  }}

On first use, Claude will walk you through OAuth authentication. See mcp/README.md for the full setup guide.

The MCP server includes built-in prompts:

  • deploy-app — Guided deployment workflow
  • debug-pod — Systematic pod diagnosis
  • getting-started — Overview of available tools and resources

What's in This Repo

sdk/├── README.md                              # This file├── server.json                            # MCP Registry manifest (see below)├── skills/│   ├── instapods-cli/│   │   └── SKILL.md                       # Skill for Claude Code (uses CLI)│   └── instapods-mcp/│       └── SKILL.md                       # Skill for Claude Desktop/Claude.ai (uses MCP tools)├── mcp/│   └── README.md                          # MCP server setup guide└── cli/    └── README.md                          # CLI quick reference

MCP Registry

InstaPods is listed in the official MCP Registry as com.instapods/instapods. server.json in this repo is the source of truth for that listing:

bash
curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=instapods"

To publish an update, bump version in server.json, then push a matching tag:

bash
git tag mcp-v1.1.0 && git push origin mcp-v1.1.0

That runs .github/workflows/publish-mcp-registry.yml, which publishes via mcp-publisher. The registry rejects a version that already exists, so every publish needs a new version.

Authentication is domain-based: the registry namespace com.instapods/* is proved by the Ed25519 public key served at https://instapods.com/.well-known/mcp-registry-auth. The workflow signs with the matching private key from the MCP_REGISTRY_PRIVATE_KEY repo secret. GitHub OIDC is not an option here — it only grants the io.github.* namespace.

Links

License

MIT

Source: README.md at commit 1133481

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.