Deploy, migrate, and sync with Staticbot skills and MCP
Connect ChatGPT to Staticbot's hosted OAuth MCP, or use three intent-focused skills with an API key in Codex CLI, Claude Code, and other coding agents.
Staticbot MCP is now hosted at https://mcp.staticbot.dev/mcp. ChatGPT users can authorize a personal plugin with the public staticbot-openai OAuth client. For Codex CLI and Claude Code, focused skills plus STATICBOT_API_KEY are the recommended setup; MCP is optional.
What the focused skills add
A capable agent could construct REST calls from scratch. The risky part is not the HTTP request — it is remembering the workflow around it. A migration must pause after discovery. A destructive sync needs review. A rollback must target an exact pinned version. DNS records must be shown without casually suggesting a nameserver change that could break mail.
Repository-aware deployment
Staticbot analyzes the repository and returns the workload, AWS or Cloudflare target, and customer-owned or Staticbot-managed ownership model.
Credential-safe fallback
When MCP is unavailable, the REST helper keeps the bearer token in STATICBOT_API_KEY, refuses absolute URLs, and does not follow redirects.
Self-navigating migrations
The agent follows pendingAction and failureBanner instead of hard-coding a brittle phase sequence.
Human decision gates
Discovery, destructive SQL, retry/skip, rollback, switchover, and deployment choices remain explicit decisions.
Get the Staticbot plugin and skills
The public staticbot-mcp repository contains all three focused skills, the optional local MCP transport, and a direct-API fallback. The hosted MCP connection is available now for ChatGPT. The public ChatGPT Plugins Directory listing is pending review, so it has to be added manually — the four steps below take about a minute.
Connect ChatGPT
- In ChatGPT, open Settings → Security and login and turn on Developer mode. On Team and Enterprise plans a workspace owner may need to allow it.
- Open Plugins, select the plus button, name the connection Staticbot, and enter
https://mcp.staticbot.dev/mcp. - Choose User-Defined OAuth Client and set
client_id=staticbot-openai, token endpoint authenticationnone, PKCE on. Staticbot does not offer dynamic client registration, so a connection made without this exact client ID will fail to authorize. - Sign in to Staticbot, approve the scopes (
staticbot:readalone for read-only), then pick Staticbot from the tools menu in a new chat.
Codex Desktop with browser control can drive this setup for you in your signed-in ChatGPT account.
Codex CLI and Claude Code
Create an organization-scoped API key at app.staticbot.dev/developer, store it as STATICBOT_API_KEY in the agent's environment, and install the Staticbot skills as personal skills. The direct REST fallback means MCP is not required.
Load the API key without putting it in shell history
printf 'Staticbot API key: ' IFS= read -rs STATICBOT_API_KEY printf '\n' export STATICBOT_API_KEY
Run this in the terminal that will launch Codex CLI or Claude Code. The key lasts for that terminal session and is inherited by the agent.
Paste into Codex CLI
Use $skill-installer to install these four Staticbot skills as personal skills from https://github.com/bitfiction/staticbot-mcp/tree/main/skills: - deploy-web-app-with-staticbot - migrate-vibe-coded-app - sync-vibe-coded-app - staticbot Do not install or configure the Staticbot MCP server. Confirm the installed paths and list all four installed skills.
Paste into Claude Code
Install these four directories from https://github.com/bitfiction/staticbot-mcp/tree/main/skills as personal Claude Code skills under ~/.claude/skills: - deploy-web-app-with-staticbot - migrate-vibe-coded-app - sync-vibe-coded-app - staticbot Copy each complete skill directory, including its scripts and references. Do not install the Staticbot plugin or configure MCP. Validate the result with "claude plugin validate ~/.claude/skills" and report the installed paths and validation result.
The collection contains deploy-web-app-with-staticbot, migrate-vibe-coded-app, and sync-vibe-coded-app. The general staticbot skill is the direct-API fallback.
OAuth for hosted chat; API keys for coding agents
Hosted ChatGPT and Claude connections open Staticbot's authorization screen, so there is no key to paste. For a read-only ChatGPT connection, select only staticbot:read; select staticbot:write during setup only for intended changes. Codex CLI, Claude Code, and optional local stdio clients use an organization-scoped key from app.staticbot.dev/developer exposed as STATICBOT_API_KEY. Never paste that key into chat or commit it.
The included helper sends the key only to the configured Staticbot origin. Hosted users need no URL configuration; local and self-hosted users can set STATICBOT_API_URL.
Try these prompts
“Use $deploy-web-app-with-staticbot to deploy this repository. Show me the detected workload, target, and ownership before starting production.”
“Use $migrate-vibe-coded-app to migrate this Firebase project to Supabase. Stop after discovery and show me exactly what will move.”
“Use $migrate-vibe-coded-app to preview this Base44 migration before switching the backend.”
“Use $sync-vibe-coded-app to inspect the latest sync run and explain every failed job. Do not retry or skip anything yet.”
“Use $deploy-web-app-with-staticbot to list safe rollback targets for my website and show the commit details.”
How skills and MCP work together
The skills are the workflow layer; MCP is an optional typed action layer. Skill-capable clients get repository-aware routing, safe sequences, and human approval gates. MCP-compatible clients also get discoverable typed tools. Without MCP, the bundled fallback skill uses the same REST API contract through a credential-safe helper.
| Focused skills | Staticbot MCP |
|---|---|
| Goal recognition and repeatable workflow | Live authenticated actions |
| Decision points and output requirements | Typed tools and input schemas |
| Direct REST fallback when needed | Production-hosted OAuth MCP plus local npm transport |
See the combined Staticbot plugin, skills, and MCP documentation for the current setup paths.
Deploy from the agent already in your repository
Install the focused skills, connect Staticbot MCP, and ask your coding agent to handle the workflow.