← usefulapi.io

INDIVIDUAL MCP TOOL

estuary_get_catalog_spec

Get one live catalog entity by its exact catalog_name, including the full serialized `spec` and compiled `built_spec`.

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

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

No auth detected

Connect to this endpoint to inspect the live schema for estuary_get_catalog_spec and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

usefulapi.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

.mcp.json

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

Settings → Connectors → Add custom connector

Name: estuary-flow-mcp
Remote MCP URL: https://estuary-flow.usefulapi.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "estuary-flow-mcp": {
      "type": "http",
      "url": "https://estuary-flow.usefulapi.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "estuary-flow-mcp",
  "transport": "streamable-http",
  "url": "https://estuary-flow.usefulapi.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • estuary_list_catalog — List live catalog entities (captures, collections, materializations, tests) the user can read, with connector + last-publication metadata.
  • 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.
  • estuary_list_connectors — List the connector catalog — available capture/materialization Docker connectors, with titles, descriptions, and logos.
  • estuary_list_connector_versions — List available versions (image tags) of connectors, with protocol and documentation URL.
  • estuary_list_drafts — List the user's draft workspaces (staging areas for catalog edits before publishing).
  • estuary_list_draft_specs — List the staged spec entries within a draft (each an insert/replace of a catalog entity pending publication).
  • estuary_list_publications — List publication history/status — each publish attempt of a draft; job_status carries the queued/success/failed outcome.
  • estuary_list_discovers — List connector discovery jobs (auto-detecting bindings/resources for a capture).