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" } }}