Skip to main content
Glama
Sign In
FronyBoard

FronyBoard

by Cafelatte1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to FronyBoard

No user-submitted related servers found.

    Related Servers

    • agent-gantt

      TobiasCoding
      A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to create and manage small project plans—including tasks, assignees, status, progress, dates, and dependencies—and retrieve Gantt-friendly project views over MCP stdio. State is stored in SQLite without external dependencies.
      10
      MIT

    • MCP Task Manager Server

      bsmi021
      A
      license
      A
      quality
      D
      maintenance
      A local Model Context Protocol server providing backend tools for AI agents to manage projects and tasks with persistent storage in SQLite, enabling structured tracking of project tasks with dependencies, priorities, and statuses.
      12
      7 npm
      25
      GPL 3.0

    • DataBook

      Ethan2298
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage and query SQLite databases through MCP tools, supporting CRUD operations, schema management, and saved views.
      4 npm
      MIT

    • taskboard-mcp

      fellam
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables deterministic, SQLite-backed task and todo tracking across multiple project scopes via MCP tools, allowing agents to add, update, list, complete, and delete tasks without hand-editing text files.
      7 npm
      MIT

    • Synapse MCP

      holaluiz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to work concurrently on the same repository by coordinating task ownership, file locks, architectural decisions, investigation gaps, handoffs, and audit activity through a local SQLite-backed MCP interface.
      14 npm
      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.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    Tools have clearly distinct purposes and descriptions explicitly guide when to use each (e.g., 'use this instead of list_tasks'). The volume of task-retrieval tools (get_task, list_tasks, search_tasks, get_status) could cause hesitation without reading the detailed cross-references, but boundaries are well-drawn.

    Naming Consistency4/5

    Mostly consistent verb_noun pattern (get_, create_, update_, list_, set_, open_/close_, upsert_, transition_). Minor deviations like 'help', 'validate', and 'recent_activity' are clear and acceptable as utility or read verbs.

    Tool Count3/5

    20 tools is on the heavy side for a project/task management server (16–25 feels heavy per the rubric). While each tool serves a purpose, some could be consolidated (e.g., set_overview and set_check, open_period and close_period).

    Completeness4/5

    Strong lifecycle coverage: projects (create/update/list/archive), tasks (create/get/update/transition/list/search), roadmaps (overview/milestone/check), periods (open/close), retrospectives, validation, and activity. Minor gaps like no explicit get_project or list_periods, but workarounds via list_projects and get_status exist.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources