Developer Tools
Meebly CLI
Manage your Meebly organizations, apps, environments, actions, and agents from the command line — no dashboard required. Install it, sign in once, and every resource you can create in the dashboard is also a command.
Install
Requires Node 18 or later.
npm install -g meeblyQuickstart
Sign in, then create an app, environment, action, and agent — the same resources you'd otherwise click through in the dashboard:
meebly login # opens your browser to sign in
meebly org list # find your org's id
meebly app create --org <orgId> --name "My App" \
--environments '[{"name":"production","backendUrl":"https://api.example.com"}]'
meebly env list --app <appId> # find the env id just created
meebly action create --environment <envId> \
--data '{"operationName":"getUser","method":"GET","path":"/users/me"}'
meebly agent create --environment <envId> \
--data '{"name":"Support Agent","instructions":"Help users with their account."}'Every command has a full --help, including every field its --data JSON body accepts:
meebly --help
meebly agent --helpAuthentication
meebly login # opens your browser, signs you in, and stores the session
meebly logout # clears the stored session
meebly status # check whether you're currently authenticated
meebly whoami # show who you're logged in as and which orgs you belong toCommands
| Resource | Commands | Notes |
|---|---|---|
org | create, list, get | No update/delete — tier is company-managed |
app | create, list, get, update, delete | |
env | create, list, get, update, delete | |
action | create, list, get, update, delete | An HTTP endpoint an agent can call |
agent | create, list, get, update, delete | Wire up actions via toolIds |
Simple fields use plain flags (--name, --org <id>); anything structured (an app's environments, an action's or agent's full body) takes JSON via --data '<json>' or --data-file <path.json>. Run meebly <resource> --help for the complete field reference of each — this includes every field the Management API also accepts, since both ride the same resource model.
Destructive commands (delete) ask for interactive confirmation unless you pass --yes.
Skip retyping ids: meebly use
meebly use --org <id> --app <id> --environment <id> # link this directory
meebly env list # --app resolved automatically
meebly use # show what's linked here
meebly use --clear # unlinkOnce linked, any command that needs --org/--app/--environment can omit the flag — it's resolved automatically from, in order: the explicit flag, MEEBLY_ORG/MEEBLY_APP/MEEBLY_ENVIRONMENT environment variables, then this directory's linked context. Run meebly use --help for details.
Scripting & agent use
Add --json to create/list/get/update on any resource for machine-readable output instead of the text shown above:
meebly org list --json
meebly action list --environment <envId> --json--json never implies --yes on delete — that confirmation stays independent so a script or agent passing --json everywhere doesn't accidentally skip it.