Alpha site Still being built

Local execution for real SaaS actions.

Cmdhub is the control plane for a suite of composable CLIs. Install tools, connect providers, inspect schemas, and pipe structured output into scripts or agents.

curl -fsSL https://cmdhub.run/install.sh | bash

cmdhub - alpha session

$ cmdhub get gmail gcal gdrive slack notion agent

[plan] install adapters: gmail, gcal, gdrive, slack, notion, agent

[ok] binaries ready

[next] connect providers with cmdhub provider connect

$ gmail message get m1 --jsonl | agent adapt --to "gcal event create"

{
  "status": "validated",
  "source_schema": "gmail.message.v1",
  "target_schema": "gcal.event.create.input.v1",
  "next": "pipe into gcal event create"
}

Brittle scripts vs. structured control.

Most SaaS automation becomes a mix of provider SDKs, local scripts, auth edge cases, and inconsistent output. Cmdhub makes the shell contract explicit.

The old way
Hard-coded tokens, inconsistent errors, and manual data reshaping.
The cmdhub way
Shared auth, JSON/JSONL streams, command schemas, and doctor checks.

Ad hoc script python3 ./utils/gmail_to_calendar.py --token "$GOOGLE_TOKEN" --raw-json

arrow_downward

cmdhub pipeline gmail message get m1 --jsonl | agent adapt --to "gcal event create"

Native adapters

The alpha is intentionally small: one control plane, core Google and Slack adapters, Notion, and a schema-aware transform CLI.

Gmail GCal MSCal GDrive Slack Notion Agent cmdhub

account_tree Schema-aware transforms

`agent adapt` sits between deterministic CLIs. It transforms one typed contract into another, validates the result, and leaves side effects to the destination CLI.

gmail message get m1 --jsonl | agent adapt --to "gcal event create" | gcal event create

shield_lock Shared auth

Use `cmdhub auth login` for the hub account and `cmdhub provider connect` for external services.

cmdhub provider connect slack --profile work

health_and_safety Doctor checks

Verify install state, credential storage, provider links, and tool-specific health before workflows fail.

data_object JSON and JSONL output

Human-readable output is the default. Switch to machine-readable JSON or streaming JSONL when a script, CI job, or agent needs to consume the result.

Technical Q&A

Is cmdhub an agent?

No. Cmdhub is the command layer. Agents can use it, but deterministic CLIs own the real app actions.

Is this an MCP server?

Not primarily. The CLI contract is the durable primitive. MCP can be one transport later.

Is everything hosted?

No. The CLIs run locally. The hosted app handles account login, registry, docs, and provider auth flows where useful.

Why alpha?

The product is still being tightened around install, auth, schemas, docs, and a small set of reliable workflows.