Skip to main content
Glama
Fabric-Pro

Fizzy MCP Server

by Fabric-Pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Fizzy MCP Server

No user-submitted related servers found.

    Related Servers

    • fizzy-mcp

      procube-cx
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Fizzy boards, cards, and projects through natural language, with full API coverage and multiple transport options.
      48 npm
      MIT

    • Fizzy MCP Server

      ryanyogan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with the Fizzy task management tool through 40 specialized tools for managing boards, cards, and comments. It supports comprehensive task operations including card creation, triaging, and user assignments with built-in retry logic and secure authentication.
      28 npm
      MIT

    • Fizzy Do MCP

      ryanyogan
      A
      license
      Not graded
      quality
      C
      maintenance
      Open-source MCP server that connects AI assistants to Fizzy (Basecamp's task management) with 70+ tools for boards, cards, workflows, and AI-powered project management.
      28 npm
      3
      MIT

    • fizzy-mcp

      clawdcraft
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Fizzy, Basecamp's open-source Kanban tool. Enables AI assistants to manage boards, cards, tags, columns, and comments via API.
      13
      48 npm
      MIT

    • ClickDown

      amscotti
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.
      53 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.8/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and the plural/singular get_* pattern makes collection versus detail calls easy to separate. The main ambiguity is between move_card_to_not_now and send_card_to_triage, which both describe returning a card to a triage-like area, and get_reactions overlaps somewhat with reaction data already exposed by get_comment.

    Naming Consistency5/5

    Every tool uses the fizzy_ prefix with clear snake_case verb_noun names. Collection endpoints consistently use plural nouns and singular endpoints use singular nouns, while create/update/delete/close/reopen/toggle follow a predictable pattern.

    Tool Count2/5

    54 tools is a very large surface for an MCP server, even though the domain is broad. Several calls (get_boards/get_board, get_users/get_user, get_columns/get_column) and many card state toggles could reasonably be consolidated, making the set heavier than necessary.

    Completeness4/5

    The server provides full CRUD and lifecycle coverage for boards, cards, comments, steps, columns, and notifications, plus file upload/retrieval and reactions. Minor gaps remain: no direct tag CRUD beyond auto-creation, no reactivate or invite user, and no delete attachment.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources