Skip to main content
Glama

Related Servers

Alternatives to forgejo-process-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Git repository operations and real-time monitoring via MCP tools, with support for WebSocket events, authentication, and observability.
      13 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables managing projects, features, tasks, dependencies, executions, and human review through a Streamable HTTP endpoint, along with persistent inter-agent cooperation via task messaging and event subscriptions. It also supports administrative actions such as approvals, cancellations, unblocking, and member management.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to start, inspect, wait for, and communicate with fleets of coding agents in worktrees, with structured status, completion events, orchestration mail, and terminal control.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables connected AI clients to inspect GitHub work, machine health, GPUs, jobs, and plans, and to request approval-gated builds, machine preparation, fixes, commands, and sandboxed multi-GPU verification of fix branches.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append validated, audited, idempotent progress events that are recorded as a matching Git commit. This keeps project truth in Git so work stays visible, resumable, and safely handable between humans and agents through scoped, short-lived credentials.
      -

    TDQS

    C2.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair (repo_create vs git_clone vs pr_merge vs ci_runs), so an agent can generally pick correctly. The main overlap is cicd_start, which bundles commit+push+watch registration and thus collides partially with git_commit/git_push, and the trio ci_runs / cicd_events / watch_list requires reading descriptions to separate.

    Naming Consistency3/5

    Two conventions coexist: resource-first names (pr_status, pr_open, repo_create, repo_list, ci_runs, watch_list) and verb-first names (git_clone, git_commit, git_push, cicd_start, cicd_events). Each family is internally readable, but the mix means `pr_open` and `git_clone` follow opposite orderings in the same set.

    Tool Count5/5

    13 tools is well within the sweet spot for a dev-workflow server and each one maps to a real step (repo, branch, commit, push, PR, CI watch). Nothing appears redundant or padded at this count.

    Completeness3/5

    The local-git-to-PR-plus-CI loop is covered, but notable gaps remain: no pr_list or PR close/comment/review, no repo_get or repo_delete, and no file read/write or git status/diff to inspect state before committing. Agents can work around some of this, but read-side PR and repo inspection are dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues