io.usefulapi由 usefulapi.io 發布官方發布者v1.39.2更新於 Nov 14, 2026
Inspect Estuary Flow captures, materializations, collections and stats.
發布方自己的服務：Ably MCP by usefulapi
託管式 MCP 伺服器，用來檢視 Estuary Flow 資料管線：目錄實體、規格、輸送量統計、連接器、草稿與發布歷史。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.usefulapi%2Festuary-flow/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"estuary-flow-by-usefulapi": {
"type": "http",
"url": "https://estuary-flow.usefulapi.io/mcp"
}
}
}Inspect Estuary Flow captures, materializations, collections and stats. Hosted, no local install.
Live endpoint: https://estuary-flow.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://estuary-flow.usefulapi.io/mcp.claude mcp add --transport http estuary-flow https://estuary-flow.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Estuary Flow credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/estuary-flow/
On first connect you'll paste your Estuary Flow credentials. They are validated, stored per-user, and scoped to you — no keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
Each paid plan covers this server only. Ask your AI to run estuary_flow_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with estuary_flow_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with estuary_flow_upgrade before then undoes the cancel. Or write to [email protected].
MIT
來源：servers/estuary-flow/README.md，提交 f22f848
List catalog entities
List live catalog entities (captures, collections, materializations, tests) the user can read, with connector + last-publication metadata. Optionally filter by a catalog-name prefix and spec_type. Estuary control-plane view live_specs_ext. PostgREST: GET /live_specs_ext.
limitoffsetspec_typename_prefixGet catalog spec
Get one live catalog entity by its exact catalog_name, including the full serialized `spec` and compiled `built_spec`. Estuary control-plane view live_specs_ext. PostgREST: GET /live_specs_ext?catalog_name=eq.<name>&limit=1.
catalog_name必填Get catalog stats
Get usage/throughput stats for one catalog entity — bytes & docs read/written (both directions), usage_seconds, warnings/errors/failures, and txn_count — per time grain. Optionally bound by a timestamp range. Estuary control-plane view catalog_stats. PostgREST: GET /catalog_stats.
grainlimitts_endts_startcatalog_name必填List connectors
List the connector catalog — available capture/materialization Docker connectors, with titles, descriptions, and logos. Optionally filter to recommended connectors. Estuary control-plane table connectors. PostgREST: GET /connectors.
limitrecommendedList connector versions
List available versions (image tags) of connectors, with protocol and documentation URL. Optionally filter by connector_id. Estuary control-plane table connector_tags. PostgREST: GET /connector_tags.
limitconnector_idList drafts
List the user's draft workspaces (staging areas for catalog edits before publishing). Estuary control-plane table drafts. PostgREST: GET /drafts.
limitList draft specs
List the staged spec entries within a draft (each an insert/replace of a catalog entity pending publication). Estuary control-plane table draft_specs. PostgREST: GET /draft_specs.
limitdraft_id必填List publications
List publication history/status — each publish attempt of a draft; job_status carries the queued/success/failed outcome. Estuary control-plane table publications. PostgREST: GET /publications.
limitList discovers
List connector discovery jobs (auto-detecting bindings/resources for a capture). Estuary control-plane table discovers. PostgREST: GET /discovers.
limitList roles
List the roles/capabilities the current credential is granted — which catalog prefixes it can read/write/admin. Read-only RPC. Estuary control-plane: POST /rpc/auth_roles.
min_capabilityGet tenant
Get the user's tenant(s) — quotas (tasks/collections), billing tiers, recurring charge, trial start, and payment provider. Estuary control-plane table tenants. PostgREST: GET /tenants.
limitView task logs
Fetch the log lines for a job by its logs_token (a UUID found on a publication, discover, or connector-tag record). Optionally page from a last-seen timestamp. Read-only RPC. Estuary control-plane: POST /rpc/view_logs.
bearer_token必填last_logged_atCreate draft
WRITE: create a new empty draft workspace (a staging area for catalog changes; does not affect live pipelines). Estuary control-plane: POST /drafts. Returns the created row.
detailUpsert draft spec
WRITE: stage (insert or replace) a catalog spec inside a draft. Edits only the draft — live pipelines are unaffected until the draft is published. Estuary control-plane: POST /draft_specs (upsert on draft_id,catalog_name). Returns the staged row.
spec必填draft_id必填spec_type必填catalog_name必填Publish draft
WRITE (DESTRUCTIVE when dry_run=false): publish a draft. dry_run=true (default) only VALIDATES the draft without changing anything. dry_run=false APPLIES the draft to the LIVE catalog — this can create, modify, or DELETE running data pipelines and their data. Set dry_run=false only when you intend to change live infrastructure. Estuary control-plane: POST /publications. Returns the publication row.
detaildry_rundraft_id必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
io.usefulapi官方發布者
針對 Ably 的託管 MCP 伺服器，讓助理檢視頻道、線上狀態與用量統計、發布訊息，並查看應用程式設定。
io.usefulapi官方發布者
唯讀存取 ROLLER 場館資料：搜尋預訂、查詢產品可用性，並查看賓客、免責聲明、禮品卡與每日報表。
io.usefulapi官方發布者
託管的 Planerio 連接器，讓助理讀取排班、人力需求、可用人員、員工資料、缺勤與年假天數。
io.usefulapi官方發布者
唯讀存取 Marmin 的阿聯酋電子發票資料：發票、貸項通知單、UBL XML、Peppol 狀態與業務檔案。
io.usefulapi官方發布者
面向 Oyster 的遠端 MCP 伺服器，讓助理讀取團隊、休假、費用、合約與發票資料，並核准或拒絕相關申請。
{ "mcpServers": { "estuary-flow": { "url": "https://estuary-flow.usefulapi.io/mcp" } }}