Fizzy CLI
The Fizzy CLI from 37signals: boards, cards, comments and search from a terminal, plus an MCP server and an agent skill.
- 250 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The client works with a Fizzy account through a personal token, and with write access an agent changes boards and cards.
- The README install runs a script from the network through `curl` and `bash`.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/basecamp/fizzy-cli/master/scripts/install.sh | bashThe first Quick Start command. Then `fizzy setup`; alternatives: Homebrew, Scoop, `go install`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The client works with a Fizzy account through a personal token, and with write access an agent changes boards and cards.
- The README install runs a script from the network through `curl` and `bash`.
This is third-party code. Review the repository files before installing.
What it does
Fizzy CLI, a command-line client for the Fizzy tracker, manages boards, cards, columns, comments, tags, webhooks and account settings from a terminal. Every command returns structured JSON with next-step breadcrumbs, and the built-in `--jq` filter trims output to the fields needed. The client ships with a `fizzy` skill and a Claude Code plugin. The `fizzy mcp` command runs an MCP server over stdio; writing is enabled by the `--writes` flag and a Read+Write token. Authentication uses a personal access token.
Who it is for. Teams tracking work in Fizzy who want Claude Code or Codex to read boards, create cards and write comments on their own.
Good fit when
- An agent files a Fizzy card for a bug found in code.
- Cards assigned to you and pinned cards are checked before planning the day.
- Webhooks and user data exports are set up with a script.
- A comment with an attachment is added to a card from the terminal.
Not a fit when
- Work is tracked in another tracker.
- The agent cannot be given a token with write access.
- Running a script from the network is unacceptable and no package manager is available.
Example request
Show my cards on the release board and add a comment with the review results to card 42.Limitations
A Fizzy account and a personal access token are required. The README install runs through `curl` and `bash`; read the script first or choose Homebrew, Scoop or `go install`. MCP write actions are enabled only by the `--writes` flag. Cards are addressed by number, other objects by id. Release candidates are not published to Homebrew and come from the Releases page, and upgrading from 3.x needs separate steps from the README.
How to disable. Remove the `fizzy` MCP entry from the client and the skill from the agent's skills directory, then revoke the personal access token in Fizzy. Uninstall the binary with the package manager that installed it.
FAQ
How do I connect Fizzy to Claude Code?
Run `fizzy setup claude`: it installs the plugin from the marketplace and links the embedded skill. For MCP use `claude mcp add fizzy -- fizzy mcp`.
How do I verify the install?
Run `fizzy doctor`. It checks the install, config, auth, API connectivity, board context and agent setup.
How do I give MCP write access?
Run `fizzy mcp --writes` and use a token with read and write rights. Without the flag, write actions are not served.
Which install methods exist?
A `curl` script, Homebrew, Scoop, `go install`, deb and rpm packages, AUR and a Windows archive from releases.
What do commands return?
Structured JSON with the `ok`, `data`, `summary` and `breadcrumbs` fields. The `--jq` filter selects the needed fields.
Discussion
No questions or reviews yet.
Related
CLI toolsThe official Basecamp CLI, with plugins for Claude Code and Codex, lets you run projects and todos from the terminal or an agent
kaiten-cli
kaiten
Command-line client and MCP server for the Kaiten tracker: cards, comments, checklists and files from the terminal or an agent
Scrumboy is a self-hosted Go task tracker with kanban boards, sprints and metrics that includes an MCP server for Cursor and Claude Code
A CLI and skill for Yandex Tracker and Wiki: short output readable by people and agents alike, instead of raw MCP payloads costing thousands of tokens
A terminal CLI and TUI for HEY mail, calendar and contacts, used by a person or by an agent
A plugin and MCP for a self-hosted task board where an agent claims a card, does the work and hands off with token telemetry.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Fizzy CLI (this card) | no | 250 | |
| Basecamp CLI | yes | 294 | works with Basecamp; Fizzy CLI targets the separate Fizzy tracker and has a built-in MCP server |
| Linear CLI | no | 1,039 | a Linear tracker client; Fizzy CLI manages Fizzy boards and cards |
README in short
The `fizzy commands --json` command prints the full CLI surface. The `--jq` filter is built in, so no external jq is needed.