Skip to main content
Glama
Germanicus1

Flow Boards MCP Server

by Germanicus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Flow Boards MCP Server

No user-submitted related servers found.

    Related Servers

    • thinker-mcp by thinker-ci

      thinker-mcpofficial

      thinker-ci
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for thinker-ci, exposing tickets, CI/CD pipelines, project management data, and AI-agent sessions as tools and resources for Claude Code and other MCP clients.
      -

    • miro-remote-mcp

      FlyAgileWithGiom
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables Claude AI to programmatically create and manipulate Miro boards via the Miro API with OAuth2 authentication. Supports 14 tools for board, item, and connector operations.
      -

    • productboard-mcp

      jonnystewart
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude to the ProductBoard API v2, enabling natural language management of notes, entities, members, analytics, Jira integrations, and webhooks.
      20 npm
      MIT

    • paperclip-mcp

      bruhsb
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes the Paperclip control plane API as tools for Claude Code agents — manage issues, coordinate agents, post comments, and orchestrate work without direct API calls.
      100
      16 npm
      2
      MIT
    • VoIPbin MCP Server by voipbin

      VoIPbin MCP Serverofficial

      voipbin
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
      52
      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

    B3.4/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools are clearly scoped to distinct resources (tickets, flows, bins, boards, comments, users, webhooks). However, update_ticket and move_ticket have overlapping functionality since update_ticket can also change the bin field, which may cause confusion.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, update_, delete_, etc.). Minor deviations like link_to_parent and unlink_from_parent still follow a predictable structure.

    Tool Count2/5

    With 38 tools, this server is over-scoped for typical MCP usage. While it covers many resources, the high number of simple list/get operations (e.g., list_flows, list_bins, list_boards, list_ticket_types) could be consolidated.

    Completeness4/5

    The tool surface covers the core ticket lifecycle (create, get, update, move, delete, archive, restore) and supports comments, linking, and webhooks. Missing functionality includes board management (no create/update/delete) and bin deletion, but these are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources