Staticbot

MCP数据服务

提供方 bitfiction · 包名 staticbot-mcp

数据服务 stdio · 本地进程 OAuth 授权 社区 / 第三方 ClaudeCursorCodexZed
查看接入方式

What Staticbot does

一句话选型结论

按资料字段整理

Staticbot 属于数据服务类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude、Cursor、Codex 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

devops supabase migrations database cdn s3 aws

支持客户端

适用场景

devopssupabasemigrations

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx -y staticbot-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Staticbot当前 未标注 stdio · 本地进程 本地部署 有 未标注
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方bitfiction上游标注的维护方 bitfiction
分类数据服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时staticbot-mcp · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

15.0 KB
来自项目仓库与上游目录的原文,未做删改

Staticbot MCP server

Give Codex, Claude, Cursor, and other MCP-compatible agents safe access to Staticbot. The server exposes typed tools for deploying websites, migrating application backends, and operating continuous sync while Staticbot keeps credentials and long-running workflow state outside the model context.

Two ways to connect

Connect the hosted server — no install, no API key. Point an MCP client that supports remote
servers with OAuth at:```text
https://mcp.staticbot.dev/mcp


You sign in to Staticbot, choose what to grant, and the client stores the connection. If you do not
have a Staticbot account yet, one is created when you first connect.

**Run it locally** — for clients that launch MCP servers as a local process. Needs Node.js 20 or
newer and a Staticbot API key from
app.staticbot.dev/developer.

Both expose the same tools. The hosted server acts as the person who authorized it and never sees an
API key; the local server uses the API key you give it.

## Install as a Codex plugin

This repository is also a Codex plugin. Its manifest bundles the Staticbot MCP server with four intent-focused skills:

- `deploy-web-app-with-staticbot` deploys a repository without making the agent choose a cloud provider. Staticbot analyzes the repo, classifies the workload, and selects the supported AWS or Cloudflare target plus its customer-owned or Staticbot-managed ownership model.
- `migrate-vibe-coded-app` moves Base44, Lovable, Bolt, or Firebase backends to customer-owned Supabase infrastructure with discovery and approval gates.
- `sync-vibe-coded-app` keeps migrated projects synchronized while preserving destructive-change review.
- `live-migrate-ai-built-app` cuts a live Lovable or Base44 app over to the migrated stack during a planned maintenance window: test migration, cutover plan, maintenance page, source write freeze, fresh final copy, verification, and domain switch. The builder-specific freeze steps are in `live-migrate-lovable-app` and `live-migrate-base44-app`.

The general `staticbot` skill remains available as a direct REST API fallback.

Add the public GitHub marketplace, then install Staticbot:```bash
codex plugin marketplace add bitfiction/staticbot-mcp
codex plugin add staticbot@staticbot

Restart the ChatGPT desktop app or Codex after adding the marketplace if Staticbot does not appear immediately. This preview plugin uses the local MCP transport, so set STATICBOT_API_KEY in the environment that launches the app. The hosted OAuth connection at https://mcp.staticbot.dev/mcp remains the lowest-friction option when you only need MCP tools rather than the bundled skills.

Install as a Claude Code plugin

Claude Code does not require Staticbot to be accepted into a central plugin registry. Add the self-hosted marketplace directly from this GitHub repository, then install the plugin:```text
/plugin marketplace add bitfiction/staticbot-mcp
/plugin install staticbot@staticbot


Set `STATICBOT_API_KEY` in the environment that launches Claude Code. The plugin starts the published `@staticbot/mcp` package with `npx` and inherits that environment; `STATICBOT_API_URL` remains optional for self-hosted or local Staticbot APIs.

The installed skills are namespaced by the plugin. For example, use `/staticbot:deploy-web-app-with-staticbot`, `/staticbot:migrate-vibe-coded-app`, `/staticbot:sync-vibe-coded-app`, or `/staticbot:live-migrate-ai-built-app`. Restart Claude Code or run `/reload-plugins` after installation if the plugin is not immediately available.

## Configure your MCP client directly

### Hosted (OAuth)

For clients that support remote MCP servers, add `https://mcp.staticbot.dev/mcp` and authorize when
prompted. The client discovers where to sign in from the server itself; there is nothing to copy or
paste, and no credential is stored on your machine.

### Local (API key)

Add the published package to your project or global MCP configuration:```json
{
  "mcpServers": {
    "staticbot": {
      "command": "npx",
      "args": ["-y", "@staticbot/mcp"],
      "env": {
        "STATICBOT_API_KEY": "sk-your-api-key-here"
      }
    }
  }
}

Hosted Staticbot at https://app.staticbot.dev is the default. Do not set STATICBOT_API_URL for the hosted service; override it only when using a self-hosted or local Staticbot API.

Keep the API key in your MCP client's secret or environment configuration. Do not paste it into chat or commit it to a repository.

What agents can do

The server groups its tools around user outcomes:

  • Analyze a public website URL for its platform, backend and supported migration/hosting paths, without requiring connected integrations
  • Inspect templates, stacks, deployments, and integration connections
  • Resolve the repository to work on from a connected GitHub or GitLab account, private repositories included
  • Create and monitor static-site and SSR deployments
  • Inspect deployment DNS, safely push deployment-owned records to linked Cloudflare zones, and recheck custom-hostname verification
  • Choose where a Cloudflare Workers app is hosted — Staticbot's account, or the user's own connected Cloudflare account — and check a hostname is deployable before creating anything
  • Choose whether an AWS-hosted static site is deployed into Staticbot's managed account or the user's own connected AWS account
  • Create a customer-owned Supabase project, wait until it is healthy, and use it as a migration target
  • Migrate Lovable, Bolt, Firebase, and Base44 projects to Supabase targets
  • Inspect migration discovery results and guide users through approval and choice gates
  • Set a migration's live-app URL, read its scan and inspect retained live-commit comparisons
  • Create previews and download portable migration packages
  • Build connected-project previews, switch live deployment to the builder branch, or sync a migration preview onto live
  • Inspect shared repository-webhook scope and explicitly set up, reset or disable GitHub push automation
  • Trigger, review, retry, or skip continuous-sync runs
  • Roll back or redeploy a website using valid pinned versions returned by Staticbot

The tool schemas and descriptions are the runtime contract seen by MCP clients. They contain the operational instructions an agent needs at the moment it selects a tool.

Website URL checks

scan_website starts or reuses an authenticated workspace check through POST /api/v1/site-scans.
It needs a Staticbot account but no repository, database, or cloud integration. Poll the returned
scan.id with get_website_scan (GET /api/v1/site-scans/{id}), waiting pollAfterMs between
requests while the scan is queued or running. Terminal results include detection, support and
hosting/migration estimates, or an explicit failure. A check never starts a deployment or migration.

This uses the existing workspace scanner with its quotas, cache, target throttle, bounded queue and
public-address protections. The anonymous marketing-page API keeps its separate Turnstile flow.
API/MCP results contain the customer summary rather than raw extracted scripts or contact history.

Connected-project operations

Read get_connected_project_operations before preview/live/webhook changes. It returns the current
builder/live branches, effective role permissions and repository-webhook consumers. Mutation tools
require explicit confirmation; live operations require those exact branch names and webhook actions
require the returned repository configuration ID. A changed target returns 409 and needs fresh
inspection and approval. Feature flags, workspace roles, persisted-link validation and agency-client
restrictions remain enforced by the backend. Webhook reset/deletion uses the existing best-effort
upstream removal, so a local configuration change is not proof that GitHub deleted the old hook.

The backend route must be deployed before enabling these tools in the hosted MCP server. See the
capability audit for the remaining dashboard/API differences.

Platform updates and pending actions

list_pending_actions and list_platform_updates expose the same post-migration fixes as the project's
Sync tab. check_platform_updates refreshes the evidence and may enqueue approved automatic fixes;
it is a mutating operation. apply_platform_updates applies the selected fixes only after the user
approves the returned effects. Customer-owned branches get pull requests, never direct pushes.
dismiss_platform_update declines optional fixes; required fixes cannot be dismissed.
refresh_platform_update re-runs the read-only refresh of an update marked canRefresh (Refresh account
connections); it installs nothing and changes no credentials or user connections. Follow the
returned sync run and PR links. The server feature flag may keep these operations disabled during rollout.

Backend controls and source updates

get_backend_workflows inspects the shared backend for exactly one connected project or migration.
Present every affected stage and the observed flags before using operate_backend_workflows.
These controls manage Staticbot's migrated Base44 scheduler on Supabase Cloud; unknown outcomes
remain unknown and are never retried automatically.

For tracked feature branches, inspect list_connected_project_previews and
get_feature_branch_preview_settings. A build requires the exact commit and build hint, including
any preview removed by the plan limit. Automatic settings keep the existing hosting-plan limits.
trigger_sync optionally redeploys all functions only after explicit confirmation; normal sync
requests stay compatible.

preview_migration_source_update resolves a chosen template version to its exact commit without
applying it. update_migration_source requires approval of that exact pair and prepares a new plan
for separate review; it does not approve target writes.

For a frontend hosted elsewhere, inspect get_external_auth_domain before approving its exact
backend and new public origin through set_external_auth_domain. This changes authentication
configuration, not frontend hosting or DNS. Even an UPDATED result needs real sign-in, reset and
magic-link testing.

Example requests

  • “Deploy this repository with Staticbot and tell me what DNS records I need.”
  • “Push this deployment's required records to my linked Cloudflare zone, then recheck verification.”
  • “Migrate my Base44 app to my Supabase project. Stop for approval before making changes.”
  • “Show me what changed in the latest sync run and explain any destructive SQL.”
  • “List valid rollback versions for this deployment, but do not roll back yet.”

Safety contract

Staticbot tools are designed around explicit human control:

  • Discovery results are presented before a migration is confirmed.
  • Choice gates are shown to the user instead of being silently defaulted.
  • Destructive sync changes pause for review.
  • Failed work is explained before an agent retries or skips it.
  • Rollbacks use an exact version returned by list_rollback_versions and require confirmation.
  • Platform updates are applied only after the user has seen each update's whatApplyingDoes and
    approved it; a required update is not approval. Customer branches get pull requests, never pushes.
  • Long-running operations return durable state that can be resumed across agent sessions.
  • The hosted server acts strictly as the person who authorized it, within the permissions they
    granted, and can reach nothing outside their own organization.

Use get_migration_overview for lightweight status polling. It returns phase/job counts, saved-report metadata, jobs needing attention and preview status, with version and pollAfterMs. It never loads raw payloads or changes the migration. Use get_migration, get_migration_jobs, discovery reports and job history for all existing technical details and before routing an action.

Migration tools are shared by the local API-key and hosted OAuth servers. Before routing any action,
check executionCompatibility.locked: locked runs cannot resume or retry, even if their old status
is IN_PROGRESS. Reports/history remain readable; start a new migration with fresh discovery and
prefer a clean target after previous writes. Hosting and Continuous Sync have independent lifecycles.

For customer-owned native Supabase sources, explicitly select sourceIntegrationInstanceId
independently of the target supabaseIntegrationInstanceId. One connection may own both projects,
or each project may use a different connection; source and target projects must differ. Lovable
Cloud has no source Management API connection and never borrows the target connection.

When a migration response contains pendingAction, the client should treat it as the source of truth for the next step. Clients should not hard-code Staticbot's internal pipeline phases.

Migration discovery can expose two additional reviewed actions. preFlightGate contains the exact
export-versus-replay choices an agent must present before calling confirm_migration with the
selected gateChoice. targetConflictReport lists objects already present on the target and offers
database, Storage, or whole-project cleanup. clean_migration_target is irreversible and requires
separate confirmation of both the exact scope and returned target project ref.

Before approval, inspect_migration_source can queue deeper inspection when the discovery report
offers it. Committing and deploying the helper in the source account requires explicit authorization
with authorizeHelperDeployment: true. Review the refreshed report before approving target writes.
list_migration_discovery_revisions and get_migration_discovery_revision expose retained reports;
execution revisions and job history preserve the evidence of past attempts.

get_migration_handoff_report returns Markdown with gaps, manual actions, remediation prompts,
a names-only secret checklist, preview and current execution evidence. An optional discovery
revision does not select historical execution. Migrated schedules remain staged inactive; the
customer reviews and runs the report's guarded activation SQL at cutover when available. It preserves
source-disabled jobs. Resolve staging errors before activation; reading a report never activates jobs.

Staticbot skills

The repository includes focused deployment, migration, and Continuous Sync skills plus a general Staticbot Skill for Codex or Claude environments that can operate the REST API directly without an MCP server. The direct-API workflow fetches the live OpenAPI contract and applies the same approval and credential-handling rules.

Use the MCP package when your client supports MCP. Use the Skill when direct API access from a command-line agent is more appropriate.

Environment variables

These apply to the local server. The hosted server needs none of them.

Variable Required Default Purpose
STATICBOT_API_KEY Yes — Authenticates requests to Staticbot
STATICBOT_API_URL No https://app.staticbot.dev Override only for a self-hosted or local API

Documentation

  • Staticbot website
  • Interactive API reference and API keys
  • npm package
  • Contributing and local verification

License

MIT

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Staticbot 怎么安装?

在客户端按下面的安装命令接入:npx -y staticbot-mcp。对应的包名是 staticbot-mcp。装完在客户端配置里引用同一个包或端点。

Staticbot 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Staticbot 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Staticbot 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Staticbot 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Staticbot 能提供哪些能力?

资料显示能力标签包括 devops、supabase、migrations、database、cdn、s3。具体工具清单以官方文档为准。

Staticbot 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

Staticbot 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。