Skip to main content
Glama
UnwantedForeignCloudProvider

forgejo-projects-mcp

by UnwantedForeignCloudProvider
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to forgejo-projects-mcp

No user-submitted related servers found.

    Related Servers

    • forgejo-mcp

      openmanbo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.
      40 npm
      MIT

    • Kanban MCP

      0xdzik
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive project management system that provides a full-featured Kanban board and dashboard accessible to AI agents. It enables agents to programmatically manage projects, tasks, and workflows through a suite of 13 specialized tools and 4 resource types.
      4
      -

    • Kanban MCP

      SawatKia
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to interact with Planka-based Kanban boards, including managing boards, lists, cards, checklists, tasks, comments, and labels through an agent-friendly MCP interface.
      13
      7 npm
      MIT

    • KittyClaw

      Ekioo
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted kanban board that dispatches AI agent fleets against tickets. The embedded Streamable HTTP /mcp endpoint exposes 7 tools to list projects, read boards and tickets, and create, move and comment tickets from any MCP client.
      26
      AGPL 3.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools target a distinct resource and action (projects, columns, issues, milestones), and descriptions clarify boundaries between close/delete, remove/delete, and get/read. A few pairs—get_project vs read_project and add_issues_to_project vs create_issue with project_id—require careful reading but are ultimately distinguishable.

    Naming Consistency3/5

    The dominant verb_noun pattern is clear (create/delete/list/close/reopen), but the set mixes synonyms: update_project vs edit_column/edit_milestone, get_project vs read_project, list_milestones vs read_milestone, plus the non-standard forgejo_status and authenticate. It remains readable but lacks a single consistent convention.

    Tool Count2/5

    At 31 tools, the surface is heavy for a Forgejo project-management server; the rubric places 25+ in the too-many range. The count is inflated by bulk variants and several full-content read_* tools that could potentially be consolidated.

    Completeness3/5

    The surface covers auth, repositories, projects, columns, cards, and milestones with CRUD and lifecycle operations. However, there is no update_issue/edit_issue for title/body/state/assignees/labels after creation, and label and assignee management is absent, leaving a notable workflow gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources