> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metabind.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Map

> How setup, inspection, authoring, release, and operations fit together

Use the workflow map to move from setup to discovery, authoring, shipping, and operations.

## Bootstrap

Prepare a machine, account, or automation session.

| Command family | Responsibility |
| - | - |
| `metabind auth` | Sign in, inspect session state, refresh, log out, and manage CLI sessions. |
| `metabind init` | Bootstrap an organization and project or continue onboarding. |
| `metabind use` | Save the active org and project context. |

## Discovery

Inspect state before changing it.

| Command family | Responsibility |
| - | - |
| `metabind status` | Summarize CLI auth, active context, project reachability, and related state. |
| `metabind doctor` | Audit project health and report repair guidance without writing. |
| `metabind bindjs` | Print the BindJS reference bundled with the installed CLI. |
| `metabind url` | Print the MCP endpoint for the active project. |
| `metabind open` | Open the current project or tool preview in the web app. |
| `metabind validate` | Validate BindJS source before upload. |

## Authoring

Create and modify components, tools, and content.

| Command family | Responsibility |
| - | - |
| `metabind component` | Manage BindJS component source and component-level history. |
| `metabind tool` | Manage MCP tools, executions, view compilation, and snapshots. |
| `metabind data-tool` | Create a data-source-backed tool as one atomic operation. |
| `metabind content` | Manage content rows, content history, publishing state, and migrations. |

## Flat-File Sync

Work on a project as files on disk instead of only through Studio.

| Command family | Responsibility |
| - | - |
| `metabind pull` | Materialize the project into a folder of files. Read-only. |
| `metabind push` | Send local file edits back to the project as drafts. |
| `metabind sync` | Maintenance for local sync state, including `sync repair`. |
| `metabind mv` | Rename an entity by moving its file, keeping its id and history. |
| `metabind inspect` | Report the secrets, hosts, and server-side code a directory declares, before pushing or installing it. |
| `metabind install` | Create a project from a directory, minting new ids and recording where it came from. |

See [Flat-File Sync](/cli/flat-file-sync) for the full workflow.

## Shipping

Move runtime package pins.

| Command family | Responsibility |
| - | - |
| `metabind publish` | Freeze draft state into a package version and update runtime pins for changed tools. |
| `metabind rollback` | Move tool pins back to an older package, or persist the target component source as a new package. |
| `metabind upgrade` | Move stale tool pins forward to a newer published package version. |
| `metabind preview` | Create and delete ephemeral preview projects, one per branch or pull request. |

## Operating

Configure and maintain a live project.

| Command family | Responsibility |
| - | - |
| `metabind env` | Manage project-wide secret bindings used by data tools. |
| `metabind api-key` | Manage project API keys for MCP host connectors. |

## Resources

Resource commands expose lower-level server objects for scripts and advanced workflows. Common resource families include projects, organizations, assets, folders, collections, tags, saved searches, dependencies, preview links, packages, and types.

Prefer the authoring and shipping families when they match the job. Use resource commands when a workflow needs direct access to an underlying object.

## Meta

| Command family | Responsibility |
| - | - |
| `metabind feedback` | Send CLI feedback with version, context, and recent command breadcrumbs attached. |
| `metabind skill` | Install, uninstall, or list the Metabind skill for supported coding tools. |

## Boundaries

* Project API keys authenticate MCP hosts, not operator CLI sessions.
* `rollback` and `upgrade` move tool pins; they do not delete package history.
* `doctor` is read-only; publishing, rollback, upgrade, and delete workflows change state.
* Component history and project package history operate at different layers.
* `pull` and `inspect` are read-only; `push`, `install`, and `mv` write local or draft state but never publish.
* `inspect` reads a directory only. It needs no project context and makes no network call.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.