Estuary Flow MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Estuary Flow MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 15 tools. Last commit 25 Oct 2026.

Inspect Estuary Flow captures, materializations, collections and stats.

Uptime history 27 days of history · worst day 99%

27 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

299 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

25 Oct a tool changed version4 times that day

24 Oct a tool changed version3 times that day

23 Oct a tool changed version

22 Oct a tool changed version

20 Oct a tool changed version3 times that day

13 Oct a tool changed version

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

1 Oct a tool changed version

and 10 more, back to 1 October 2026

Nothing serious here today

Today is the operative word: we check Estuary Flow MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add estuary-flow --transport http https://estuary-flow.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://estuary-flow.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.estuary-flow]
url = "https://estuary-flow.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "estuary-flow": {
      "url": "https://estuary-flow.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "estuary-flow": {
      "type": "http",
      "url": "https://estuary-flow.usefulapi.io/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

estuary

estuary_create_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.

estuary_get_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.

estuary_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.

estuary_get_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.

estuary_list_catalog

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.

estuary_list_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.

estuary_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.

estuary_list_discovers

List connector discovery jobs (auto-detecting bindings/resources for a capture). Estuary control-plane table discovers. PostgREST: GET /discovers.

estuary_list_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.

estuary_list_drafts

List the user's draft workspaces (staging areas for catalog edits before publishing). Estuary control-plane table drafts. PostgREST: GET /drafts.

estuary_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.

estuary_list_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.

estuary_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.

estuary_upsert_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.

estuary_view_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.

Endpoints

URL	Transport	State	Latency	Checked
https://estuary-flow.usefulapi.io/mcp	streamable-http	answering	166 ms	1 min ago

Alternatives to Estuary Flow MCP by usefulapi

same job, measured the same way

Codat MCP by usefulapi

by usefulapi

MCP server for Codat — companies, connections, invoices, bills and financial statements.

28 tools answering

api.video MCP by usefulapi

by usefulapi

Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.

15 tools answering

GitBook MCP by usefulapi

by usefulapi

Read spaces, collections, pages and content; search docs and manage GitBook organization spaces.

14 tools answering

Moosend MCP by usefulapi

by usefulapi

Inspect Moosend lists, subscribers, segments and campaign stats, and add or unsubscribe subscribers.

20 tools answering

Depot MCP by usefulapi

by usefulapi

Inspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs.

24 tools answering

Hypertune MCP by usefulapi

by usefulapi

Evaluate and inspect your Hypertune feature flags from your AI assistant.

5 tools answering

MCP Bruno

by kta41

Python MCP server for running and inspecting Bruno API collections.

123 installs/wk local only

Codemagic MCP by usefulapi

by usefulapi

Trigger and inspect Codemagic CI builds, apps and artifacts.

9 tools answering

Estuary Flow MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Estuary Flow MCP by usefulapi do?

It exposes 15 tools, read directly from the server on our last check. Among them: estuary_create_draft, estuary_get_catalog_spec, estuary_get_catalog_stats, estuary_get_tenant, estuary_list_catalog, estuary_list_connectors and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Estuary Flow MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 299 ms. The bar chart above shows every period we have measured.

How do I connect Estuary Flow MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Estuary Flow MCP by usefulapi need an API key?

No. Estuary Flow MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Estuary Flow MCP by usefulapi?

It answers our handshake in 299 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Estuary Flow MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at estuary-flow.usefulapi.io, which runs on its operator's own terms.