Fizzy
Let your coding agent list, create, and update tasks in Fizzy without leaving Claude Code or Cursor.
Overview
io.github.davegomez/fizzy is a MCP server for the Build phase that connects coding agents to Fizzy task management via API token auth.
What is this MCP server?
- stdio MCP package @silky/fizzy-mcp v1.0.0 with npm install path
- Authenticates with required FIZZY_TOKEN secret env var
- Optional FIZZY_BASE_URL for non-production or custom API hosts
- Optional FIZZY_ACCOUNT slug for default workspace context
- Task-management tools exposed over Model Context Protocol for agent-driven updates
- server.schema.json version 1.0.0
- npm package @silky/fizzy-mcp transport stdio
- 3 configurable environment variables (1 required secret)
Community signal: 2 GitHub stars.
What problem does it solve?
Switching between your agent and Fizzy to update tasks breaks flow and lets backlog drift out of sync with what you are actually building.
Who is it for?
Solo builders who already use Fizzy and want Claude Code or Cursor to create, assign, or close tasks while implementing features.
Skip if: Teams that do not use Fizzy or anyone who needs deep reporting without granting API access via FIZZY_TOKEN.
What do I get? / Deliverables
Your agent can query and update Fizzy tasks in-thread so the board reflects the same priorities you are coding against.
- Registered stdio MCP server pointing at Fizzy
- Agent-callable Fizzy task operations scoped by your token
- Optional multi-account routing via FIZZY_ACCOUNT and custom API base URL
Recommended MCP Servers
Journey fit
Solo builders manage build backlogs and shipping tasks during the Build phase; Fizzy is where that work is tracked day to day. PM subphase covers task boards, priorities, and execution tracking—exactly what a Fizzy MCP bridges into the agent session.
How it compares
Fizzy API MCP integration, not a standalone project-management skill or template repo.
Common Questions / FAQ
Who is io.github.davegomez/fizzy for?
Indie developers and small teams on Fizzy who want their AI coding agent to manage tasks through MCP instead of manual UI updates.
When should I use io.github.davegomez/fizzy?
Use it during active Build and Ship work when you want the agent to sync implementation progress with your Fizzy board in real time.
How do I add io.github.davegomez/fizzy to my agent?
Install @silky/fizzy-mcp from npm, add the stdio MCP server entry in Claude Code or Cursor, and set FIZZY_TOKEN plus optional FIZZY_BASE_URL and FIZZY_ACCOUNT.