Skip to main content
Glama
davegomez

fizzy-mcp

by davegomez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fizzy-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      49 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.
      10 npm
      3
      MIT

    • workspace-board-mcp

      FURYER
      F
      license
      A
      quality
      C
      maintenance
      MCP server for workspace kanban boards, enabling board operations like get, add, update, move, delete cards and columns.
      8
      -

    • kaiten-mcp

      DVZak
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with Kaiten project management through its REST API. Enables managing spaces, boards, cards, comments, checklists, tags, and time logs.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a clear primary purpose: get_card retrieves details, search finds cards, task creates/updates, step manages checklist items, comment handles comments, boards lists boards, and account manages sessions. There is minor overlap between task and step (both can interact with steps), but the descriptions clearly delineate when to use each (task for card-level operations, step for direct step manipulation).

    Naming Consistency3/5

    All tools share the 'fizzy_' prefix, but the action part mixes verbs (get_card, search) with nouns (step, task, comment, boards, account). The nouns imply CRUD operations without a consistent verb pattern. While readable, the naming is not as uniform as a strict verb_noun convention.

    Tool Count5/5

    Seven tools cover the core domain of a card-based project management system: boards, cards, search, steps, comments, and account management. Each tool is necessary and there is no redundancy or bloat. This is a well-scoped set for the server's purpose.

    Completeness3/5

    The surface covers creation, retrieval, updating, and search of cards, plus step and comment management and board listing. However, there is no explicit card deletion tool, and board management beyond listing is absent. These are notable gaps for full lifecycle coverage, particularly the inability to permanently remove a card.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources