CLI

The GooseWorks CLI installs the GooseWorks skill catalog into your coding agent (Claude Code, Cursor, Codex). A master skill file teaches your agent how to search and run 100+ ready-made skills — Reddit / X / LinkedIn scraping, email finding, prospect enrichment, competitor research, and more. Data-provider calls and media generation can use GooseWorks credits.

CLI vs MCP. The CLI and the GooseWorks MCP server are two different things, and install --claude --mcp (or install --all) sets up both. The MCP provides account tools for files, chat history, automations, and Ad Remixer. The CLI additionally installs local skill files. You can have the MCP without local skills (that’s what the hosted connectors give you), but one CLI install gives you both.

Install

Paste this into your coding agent — Claude Code, Cursor, or Codex — and let it run the install:

Install GooseWorks: run `npx gooseworks@latest install` with the flag for my agent (--claude, --cursor, or --codex) and --mcp. If a browser doesn't open, print the sign-in URL. When installation finishes, tell me to restart the agent. After I restart, call the GooseWorks account_whoami tool to confirm the connection. Then continue my first GooseWorks task, completing any unfinished onboarding if needed. At the taste step, open the visual GooseWorks taste-picker page instead of listing cards in the terminal.

The agent runs the install and can print the sign-in URL if no browser opens. Restart your agent when installation finishes so it loads the MCP connection. After restarting, account_whoami verifies access through that connection. No special onboarding command is required. The agent chooses its editor flag and includes --mcp. After you restart it, ask it to call account_whoami to verify the MCP connection. CLI commands on this page were verified against published gooseworks@0.3.16 on September 9, 2026. Install signs you in, adds skills, and registers MCP. Then verify the connection:

Signs you in with Google in your browser, and saves credentials to ~/.gooseworks/credentials.json
Installs the GooseWorks skills to ~/.agents/skills/ and links them where your agent looks
Registers the gooseworks MCP server in your agent’s config (~/.claude.json, ~/.codex/config.toml, or Cursor’s mcp.json)
Restart your coding agent, then ask: “Use the GooseWorks account_whoami tool to tell me which account is connected.” A successful tool response verifies the connection.

Restart after installation, before checking the connection. This reloads your coding agent’s MCP configuration so the GooseWorks tools are available.

Manual install

Prefer the terminal? The same thing, typed by hand:

Manual install

npx gooseworks@latest install --claude --mcp    # or --cursor --mcp, --codex --mcp, --all

Then restart your agent and ask it to call account_whoami. Once that succeeds, ask GooseWorks to do a real task. If company setup is incomplete, onboarding starts automatically before the task continues.

Requirements

Node 18 or newer — check with node --version. npx ships with it.
A browser on the same machine for Google sign-in. If none opens automatically, the CLI prints the sign-in URL — paste it into any browser and finish there.

Claude Code

Connect Claude Code with skills and MCP:

npx gooseworks@latest install --claude --mcp

Complete browser sign-in, restart Claude Code, then ask it to call account_whoami to verify your connection.

Codex

Connect Codex with skills and MCP:

npx gooseworks@latest install --codex --mcp

Complete browser sign-in, restart Codex, then ask it to call account_whoami to verify your connection.

Install flags

Flag	What it does
`--claude`	Configure Claude Code (`~/.claude.json`)
`--cursor`	Configure Cursor (global + any project `.cursor/mcp.json`)
`--codex`	Configure Codex (`~/.codex/config.toml`)
`--all`	Configure every detected coding agent, including MCP
`--mcp`	Register the MCP server as well as installing skills; include this with an agent-specific flag
`--with <slug>`	Also install a standalone skill (repeatable)
`--ref <code>`	Attribute the signup to a referral or campaign code

# Skills and MCP for one agent
npx gooseworks@latest install --claude --mcp

# Skills and MCP for every detected agent
npx gooseworks@latest install --all

# Optional: check local video-rendering prerequisites
npx gooseworks doctor

Pass --mcp explicitly with --claude, --cursor, or --codex. The published CLI requires it for those installs; --all already includes MCP.

See MCP Servers for what the server provides.

Onboarding and taste selection

You do not need a special onboarding command. Ask GooseWorks to do a normal task, or say “Set up GooseWorks for https://yourcompany.com.” The agent preserves that request while it completes any missing company setup. When you reach Your taste, the agent opens or shows one Choose your taste in GooseWorks link. Use the visual card picker in your browser to love or skip ads, then click Continue or Skip this. Return to the agent and reply done; it reloads the shared onboarding state and continues from the next step. The CLI should never print a numbered list of taste-card titles or ask you to choose visual styles without showing the images.

Verify your MCP connection

After restarting your coding agent, ask:

Use the GooseWorks account_whoami tool to tell me which account is connected.

A successful tool response confirms that the client can call GooseWorks with your credentials. If the tool is unavailable, check that the gooseworks server is enabled in the client’s MCP settings, rerun the install with your client flag and --mcp if needed, then restart the client.

Check local video prerequisites — `doctor`

Use this when you plan to render video ads locally with goose-video-local:

npx gooseworks doctor

In version 0.3.16, the report checks:

Check label	What it checks
`Logged in`	Saved login credentials exist
`GooseWorks MCP configured`	The saved credentials contain an MCP server URL
`ffmpeg on PATH`	The local video encoder is available
`ffprobe on PATH`	The local media-inspection tool is available
`Playwright (Chromium renderer)`	The Playwright command is available directly or through `npx`

A missing check prints a suggested fix and makes the command exit with code 1. It has no command-specific options. It does not contact the MCP server, validate the token, or inspect your agent’s MCP configuration.

Missing ffmpeg, ffprobe, or Playwright matters for local video rendering. Those tools are not required for MCP access or cloud-generated static ads. Verify MCP access separately with account_whoami in your restarted agent.

What happens after install

Your coding agent gets a new skill that teaches it how to use the full GooseWorks toolkit. When you ask it to do any data task — scraping, research, lead generation, enrichment — it will automatically search the GooseWorks skill catalog, fetch the right skill, and run it. The agent also gets direct tool access to files, chat history, automations, and Ad Remixer through the MCP server. It can call catalog_search(type: "skill") and catalog_fetch(type: "skill") to load GooseWorks instructions on demand, even for a skill such as goose-video that isn’t installed locally. Example prompts you can try:

“Scrape the top posts from r/ClaudeAI on Reddit”
“Find the email address for the CEO of Acme Corp”
“Research competitors of Linear.app”
“List the files in my agent workspace”
“What did my agent and I talk about last week?”
“Create a daily automation at 9am that pulls new Linear issues into my workspace”
“Make three ads for acme.com” — see the quickstart

Commands

Command	What it does
`npx gooseworks@latest install --claude --mcp`	Sign in and install skills and MCP for Claude Code
`npx gooseworks@latest install --cursor --mcp`	Connect Cursor
`npx gooseworks@latest install --codex --mcp`	Connect Codex
`npx gooseworks install --all`	Connect every detected agent
`npx gooseworks doctor`	Check saved login, saved MCP URL, and local video prerequisites
`npx gooseworks whoami`	Show which account you’re signed in as
`npx gooseworks login`	Sign in (install does this for you)
`npx gooseworks update`	Update to the latest skill version
`npx gooseworks credits`	Check your credit balance
`npx gooseworks search "query"`	Search the skill catalog
`npx gooseworks logout`	Sign out and clear credentials

How skills run

When your coding agent uses a GooseWorks skill:

It searches the skill catalog to find the right skill for your task
It downloads the skill’s instructions and scripts
It saves scripts to a temporary directory (never your project folder)
It runs the scripts with the right parameters
API calls go through GooseWorks proxy — you never need to manage API keys

Credits

Data-provider calls and media generation can cost credits. Your starter grant depends on how the account was created; check your actual balance instead of assuming a fixed amount. Ask your agent to show a generation quote before it spends credits. Check your balance anytime:

npx gooseworks credits

You can top up credits from the Billing page in the web dashboard.

Credentials

Your login credentials are stored at ~/.gooseworks/credentials.json. This file contains your API key, email, the API base URL, and (if the backend provides it) mcp_server_url for the GooseWorks MCP server. To switch accounts or environments, log out and log back in:

npx gooseworks logout
npx gooseworks@latest install --claude --mcp

Restart your coding agent, then ask it to call account_whoami to confirm the connected account.

Getting started

Skill catalog

Reference

Install

Manual install

Requirements

Claude Code

Codex

Install flags

Onboarding and taste selection

Verify your MCP connection

Check local video prerequisites — `doctor`

What happens after install

Commands

How skills run

Credits

Credentials

​Install

​Manual install

​Requirements

​Claude Code

​Codex

​Install flags

​Onboarding and taste selection

​Verify your MCP connection

​Check local video prerequisites — doctor

​What happens after install

​Commands

​How skills run

​Credits

​Credentials

Install

Manual install

Requirements

Claude Code

Codex

Install flags

Onboarding and taste selection

Verify your MCP connection

Check local video prerequisites — `doctor`

What happens after install

Commands

How skills run

Credits

Credentials