Skip to main content
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 agent — Claude Code, Cursor, Codex, or a chat app like Claude or ChatGPT:
Your agent reads that page and follows it. It asks you before it installs anything, then runs the GooseWorks CLI with --all (it sets up every coding agent on your machine at once), opens a browser for Google sign-in, checks the install, and carries on in the same chat: it sets up your brand there (it asks for your website and a couple of quick questions), then gets back to what you asked for. You don’t need to reopen your agent; the GooseWorks tools also show up in its next session. If your agent is a chat app like claude.ai, the Claude desktop app’s chat or ChatGPT, it gives you the MCP connector address instead. The page only ever runs npx gooseworks@latest …. It writes your agent’s skills folder, your agent’s MCP config (for Cursor that is the global Cursor MCP config, plus the project’s .cursor/mcp.json if the folder has one), and ~/.gooseworks/credentials.json. The MCP config entries contain your sign-in token. It writes no other files. Installing is free; some skills spend credits when they run. The check at the end also reports whether ffmpeg and a browser are present; those only matter for rendering video ads on your machine and do not block the install. The agent runs the install with --all --mcp, checks the connection with account_whoami, and sets up your brand in the same chat. You don’t need to restart it. The instructions the agent follows live at gooseworks.ai/install.md; you can read them yourself. CLI commands on this page were verified against published gooseworks@0.4.4 on October 5, 2026. What the agent does:
  1. Signs you in with Google in your browser, and saves credentials to ~/.gooseworks/credentials.json
  2. Installs the GooseWorks skills to ~/.agents/skills/ and links them where your agent looks
  3. Registers the gooseworks MCP server in your agent’s config (~/.claude.json, ~/.codex/config.toml, or Cursor’s mcp.json)
  4. Checks the connection with account_whoami. In the session that ran the install, the agent calls GooseWorks through npx gooseworks@latest tool …; from your agent’s next session the GooseWorks MCP tools are listed directly.
  5. Sets up your brand in the chat, then carries on with what you asked for.

​
Run it yourself

Prefer the terminal? The same thing, typed by hand:
Then open a new session of your agent and ask it to call account_whoami. Once that succeeds, ask GooseWorks to do a real task. If your brand isn’t set up yet, the agent sets it up in the chat 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:
Complete browser sign-in, open a new Claude Code session, then ask it to call account_whoami to verify your connection.

​
Codex

Connect Codex with skills and MCP:
Complete browser sign-in, open a new Codex session, then ask it to call account_whoami to verify your connection.

​
Install flags

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.

​
Brand setup

You do not need a special setup command. Ask GooseWorks to do a normal task. If your brand isn’t set up yet, the agent asks for your website and follows the setup steps returned by GooseWorks in the chat. Then it carries on with your original request.

​
Verify your MCP connection

In a new session of 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:
In version 0.3.16, the report checks: 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 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-ads 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

​
How skills run

When your coding agent uses a GooseWorks skill:
  1. It searches the skill catalog to find the right skill for your task
  2. It downloads the skill’s instructions and scripts
  3. It saves scripts to a temporary directory (never your project folder)
  4. It runs the scripts with the right parameters
  5. 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:
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:
Open a new session of your coding agent, then ask it to call account_whoami to confirm the connected account.