MCP server for Fizzy task management
Connect Fizzy to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Fizzy task management. The fizzy mcp server is what makes that connection.
MCP server for Fizzy task management. Exposes 7 tools for managing boards, cards, comments, and checklists.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
fizzy_account — The fizzy_account tool exposed by this serverfizzy_boards — The fizzy_boards tool exposed by this serverfizzy_search — *Date range values: today, yesterday, thisweek, thismonth, last7, last14, last30fizzy_get_card — *Provide card_number OR card_id. Prefer card_number when you have the human-readable # from the UIfizzy_task — The fizzy_task tool exposed by this serverfizzy_comment — The fizzy_comment tool exposed by this serverfizzy_step — The fizzy_step tool exposed by this serverConfiguration is passed through the environment: FIZZY_TOKEN, APPDATA, FIZZY_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Get your Fizzy access token: 1. Log in to Fizzy 2. Go to Settings > API Access 3. Generate a new token
The server ships on npm as @silky/fizzy-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fizzy's toolset — fizzy_account, fizzy_boards, fizzy_search and 4 more — is a fair guide to whether it matches your workflow. It is maintained by davegomez; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| fizzy_account | The fizzy_account tool exposed by this server. |
| fizzy_boards | The fizzy_boards tool exposed by this server. |
| fizzy_search | \*Date range values: today, yesterday, thisweek, thismonth, last7, last14, last30. |
| fizzy_get_card | \*Provide card_number OR card_id. Prefer card_number when you have the human-readable # from the UI. |
| fizzy_task | The fizzy_task tool exposed by this server. |
| fizzy_comment | The fizzy_comment tool exposed by this server. |
| fizzy_step | The fizzy_step tool exposed by this server. |
{
"mcpServers": {
"Fizzy": {
"command": "npx",
"args": ["-y", "@silky/fizzy-mcp"],
"env": {
"FIZZY_TOKEN": "your-token-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Get your Fizzy access token: 1. Log in to Fizzy 2. Go to Settings > API Access 3. Generate a new token
| Variable | Description | Required |
|---|---|---|
| FIZZY_TOKEN | Credential the server authenticates with. | Yes |
| APPDATA | Configuration value read at startup. | Optional |
| FIZZY_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.