MCP.so
ログイン

Fizzy MCP

@davegomez

Fizzy MCP について

MCP server for Fizzy task management

基本情報

カテゴリ

その他

ライセンス

AGPL-3.0

ランタイム

node

トランスポート

stdio

公開者

davegomez

投稿者

David Gomez

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "fizzy": {
      "command": "npx",
      "args": [
        "-y",
        "@silky/fizzy-mcp"
      ],
      "env": {
        "FIZZY_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Fizzy MCP?

Fizzy MCP is an MCP server for Fizzy task management. It exposes 7 tools for managing boards, cards, comments, and checklists, designed for use by AI assistants to interact with Fizzy projects.

How to use Fizzy MCP?

Obtain a Fizzy access token from Settings > API Access in the Fizzy app. Then configure the server in your MCP client (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, or Continue) using the command npx -y @silky/fizzy-mcp and setting the FIZZY_TOKEN environment variable. Optionally set FIZZY_ACCOUNT for a default account slug and FIZZY_BASE_URL for a custom API base URL.

Key features of Fizzy MCP

  • 7 tools for boards, cards, comments, and checklists
  • Supports multiple MCP clients (Claude, Cursor, VS Code, etc.)
  • Account resolution with fallback: explicit, session, env, or auto-detect
  • Pagination support for board and search results
  • Filter cards by tags, assignees, status, dates, and more
  • Create and update cards with markdown descriptions and checklist steps

Use cases of Fizzy MCP

  • AI assistants can list and search Fizzy boards and cards
  • Create or update tasks directly from chat conversations
  • Manage comments and checklists on cards
  • Automate task triage and status updates

FAQ from Fizzy MCP

How do I get a Fizzy API token?

Log in to Fizzy, go to Settings > API Access, and generate a new token. Use it as the FIZZY_TOKEN environment variable.

What environment variables are required?

FIZZY_TOKEN is required. Optional variables are FIZZY_ACCOUNT (default account slug) and FIZZY_BASE_URL (API base URL, default https://app.fizzy.do).

How does account resolution work?

Tools resolve account_slug in this order: explicit parameter on the tool call, session default set via fizzy_account tool, FIZZY_ACCOUNT environment variable, or auto-detect if the user has exactly one account.

What transports are supported?

The server uses stdio transport, configured via command and args in the MCP client configuration. No HTTP or other transports are mentioned.

What are the 7 tools provided?

The tools are: fizzy_account (get/set/list accounts), fizzy_boards (list boards), fizzy_search (search cards with filters), fizzy_get_card (get card details), fizzy_task (create or update cards), and fizzy_comment (create, list, update, delete comments). A seventh tool is implied for checklists.

コメント

「その他」の他のコンテンツ