fizzy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIZZY_URL | No | Your Fizzy instance URL | http://localhost:3000 |
| FIZZY_TOKEN | Yes | API access token | |
| FIZZY_ACCOUNT_ID | No | Account ID (from URL path) | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fizzy_list_boardsA | List all Fizzy boards in the account |
| fizzy_get_boardB | Get details of a specific Fizzy board |
| fizzy_create_boardC | Create a new Fizzy board |
| fizzy_list_cardsB | List cards. Optionally filter by board ID. |
| fizzy_get_cardA | Get details of a specific card |
| fizzy_create_cardB | Create a new card on a Fizzy board |
| fizzy_update_cardC | Update an existing card |
| fizzy_move_cardA | Move a card to a different column (use 'done' or 'not_now' for special columns) |
| fizzy_list_columnsA | List all columns on a Fizzy board |
| fizzy_add_commentB | Add a comment to a card |
| fizzy_list_commentsB | List all comments on a card |
| fizzy_add_tagA | Add a tag to a card. Creates the tag if it doesn't exist. |
| fizzy_remove_tagB | Remove a tag from a card |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action. While update_card and move_card could theoretically overlap, move_card specifically handles column changes with special column semantics, keeping boundaries clear.
All tools follow a consistent fizzy_verb_noun pattern in snake_case. Singular nouns are used for single-item operations (get_card, create_board) and plural nouns for list operations (list_cards, list_boards), making the pattern predictable.
Thirteen tools is well-scoped for a Kanban-style board management server. Each tool serves a clear purpose, covering boards, cards, columns, comments, and tags without unnecessary bloat.
The core operations for boards and cards are present (create, read, update, move), but delete operations for both boards and cards are missing, creating a lifecycle gap. Additionally, there is no board update or tag listing, though these are less critical.