Ezeo CLI

One package, one command registry. "ezeo <command>" is the CLI and "ezeo mcp" serves the same commands to any MCP-capable agent, so a command that works in the terminal works identically inside Claude Code or Codex.

It is for anyone who owns, administers or belongs to an Ezeo organization: the Ezeo team and self-serve customers alike. Client accounts use the web app. The CLI acts as the logged-in user, so row-level security, organization membership and the spend caps gate every call, and it never uses a service-role key. "ezeo login" refuses a client account and stores nothing.

If "ezeo whoami" says your organization holds zero projects, add your site at https://ezeo.ai/app, or, if you installed Ezeo through the Ezeo Shopify app, claim your store at https://ezeo.ai/app/shopify/link.

Requires Node 22 or newer. Install the package from npm, then sign in:

npm i -g @ezeo/cli

ezeo login
ezeo whoami

Every command then runs as "ezeo <command>". Run the same install command again to update.

"ezeo login" with no flag opens the browser sign-in (Google). Google always shows its account chooser, so pick the account whose Ezeo access you want the CLI to have. The terminal then prints who you are signed in as.

ezeo login
ezeo login --password
ezeo whoami

"ezeo login --password" asks for email and password in the terminal, for a machine with no browser; they are never read from argv or the environment. The session is stored at ~/.config/ezeo/credentials.json (mode 0600). "ezeo logout" removes it.

Choose a project, highest wins: --project, then the EZEO_PROJECT variable, then project = "Name" in a .ezeo.toml searched upward from the working directory, then whatever "ezeo use" stored. Names match by prefix; an ambiguous prefix is an error that lists the candidates.

Every command accepts --json. Absence renders as a dash in tables and as null in JSON, never as 0.

Cost classes

• free Reads data Ezeo already holds. Nothing is spent.
• llm One OpenRouter call, billed to the project.
• dfs DataForSEO spend against the shared monthly caps.
• scrape One Firecrawl page scrape, billed to Ezeo.
• pipeline Starts or resumes article runs, each with LLM and image spend.

Every llm, dfs, scrape and pipeline command prints what it will cost before it runs. In a terminal it then runs, so press Ctrl-C if the cost is not what you want; when stdin is not a terminal, the command needs --yes. If the cost policy refuses a command it exits with code 5 before any network call, so nothing was spent.

Inside an MCP client there is nobody to prompt, so a paid tool first returns a dry run and a confirm code, and runs only when called again with the same input and that code. The code is bound to the tool and its exact input and dies with the server process. It is not single-use, so each confirmed call can spend again.

The two approve commands take a required --hash taken from "ezeo articles show", which prints it beside the article body. There is no default and no lookup, so an article cannot be approved without having been read. "ezeo articles cancel" spends nothing but cannot be undone.

"ezeo mcp" serves the registry over stdio. "ezeo setup" registers it with an agent for you and prints exactly what it runs; add --dry-run to print without changing anything.

ezeo setup claude
ezeo setup codex
ezeo setup grok
ezeo setup gemini
ezeo setup cursor
ezeo setup claude --dry-run

Install the agent reference as a Claude skill so an agent knows the rules before it calls anything. "ezeo help --agent" prints the reference and "ezeo skill install" writes it to ~/.claude/skills/ezeo/SKILL.md.

ezeo help --agent
ezeo skill install
ezeo skill install --dry-run

Over MCP a tool call still working after 45 seconds returns STILL RUNNING and a job id; the ezeo_job tool collects the result.

• 0: ok
• 1: usage, such as a bad flag or an ambiguous project
• 2: not logged in, or the role is refused
• 3: the server answered and said no
• 4: the request never reached the server
• 5: refused locally by cost policy; nothing was spent