Skip to main content

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.

Set up the CLI once, then reuse the same authenticated session for project authoring, publishing, and operations.

​
Requirements

  • macOS or Linux.
  • Homebrew.
  • A Metabind account. To connect an existing project, your account needs access to its organization.

​
Install

1

Install with Homebrew

brew install metabindai/tap/metabind
2

Open the CLI

metabind help
Update an existing install with Homebrew: 
brew update
brew upgrade metabind

​
Sign In

Start with the interactive login flow: 
metabind auth login
The CLI stores a refreshable operator session in the user config directory. This session is separate from project API keys used by MCP hosts. Use metabind auth to inspect, refresh, or end CLI sessions.

​
Connect a Project

Most project work needs two context values:
  • organization
  • project
Choose the organization and project you want to operate on, then save that scope with metabind use. If you only know the project, the CLI can try to discover its organization from the orgs your account can access. For a new workspace or invitation flow, start with metabind init. It can create an organization and project, accept an invitation, or poll an onboarding job. The active scope is saved for the OS user account. If multiple command-driven runs share the same OS user, isolate them with separate config directories before they work on different projects.

​
Confirm Access

Check the session and active project: 
metabind status
Then run a read-only project command: 
metabind component list
If the command returns successfully, the CLI can reach the project. Continue with Workflow Patterns to author, probe, publish, or roll back changes.

​
Troubleshooting

Homebrew installed the binary outside your shell path. Check Homebrew’s installation prefix and make sure the matching bin directory is on your path.
The auth session or saved project context may not match. Check metabind status, then update the saved scope with metabind use.
Project auto-discovery needs a valid session and access to the owning organization. Save the missing context value explicitly before continuing.
Update with Homebrew. The help output and bundled BindJS reference come from the installed release.

​
Next Steps

Context Resolution

Learn how the CLI decides where a project command lands.

Workflow Patterns

Follow durable loops for authoring, probing, publishing, and rollback.