Connector Tool Catalogs

StackJack provides a broad and growing catalog of connector tool families. The exact per-connector counts are in the generated table below, whose total also includes the platform tools. These docs include one reference page for every connector, listing each tool's name, description, parameter table, safety classification, and required plan tier.

Start at the Connector Tools Reference index — it links every per-connector page and carries the same generated per-connector counts.

The per-connector reference pages are generated directly from StackJack's live tool catalog. Tool counts and tier assignments change as connectors grow, and these pages are regenerated with every release.

What this reference is, and what it is not. It is the release inventory — every tool that ships in this build of StackJack. It is not the tool set your session is served. Yours is narrower, and depends on which connectors your organization subscribes to, each subscription's plan, the tool selection on your MCP client and your own grants, whether the connector is configured, and the catalog mode your connection resolves to. Expect the reference to list tools you do not have; use stackjack_list_tools or stackjack_get_catalog_mode to see what a given connection actually holds.

"Coming soon" connectors cannot be configured. A connector can appear in the catalog and in the counts while StackJack still holds it back from customer use — Datto SaaS Protection is the one in that state today. Its tools are real code with real reference pages, but there is no way to connect it, so nothing it lists is callable.

The parameter tables are a human-readable rendering of each tool's real parameters. From a connected harness, use stackjack_get_tool_catalog with schemas included—or stackjack_describe_tools while catalog mode is active—when the AI needs the machine-readable JSON input schema.

You can also browse two related live projections. They answer different questions from the release-wide generated reference:

• In the portal: open Connectors, open the connector's panel, and select API Permissions. The planner shows that connector's full code catalog—including above-plan tools—grouped by category with plan badges, because it is a permission-planning surface rather than an execution grant. The /permissions deep link offers the same planner with a connector selector (guide).
• From a connected AI: ask it to run stackjack_list_tools. That diagnostic response contains platform tools plus connector families whose credentials loaded for the current request, and marks each row accessible or inaccessible under the current plan and grants. A transient credential-load failure can omit a subscribed connector from this projection; use stackjack_health_check when an expected family is absent.

Connector families at a glance

The counts below are generated directly from the shipped tool catalog — they are exact for the release this page shipped with.

Plus the StackJack platform tools (stackjack_) that work without any connector — the Platform row in the table above.

What each generated reference page includes

• Every tool name and its plain-language description.
• Required plan tier per tool (Free / Pro / Business).
• Read-only vs write/destructive classification.
• Connector-specific conventions: pagination style and page-size caps, ID discovery patterns, and any special behaviors (for example, report tools that return secure download links instead of raw JSON).