GitFlic MCP Server
Related Servers
Alternatives to GitFlic MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for GitFlic, the Russian Git hosting platform, enabling AI agents to manage projects, issues, merge requests, files, and more via 66 tools covering 13 API categories.6611 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceFull-coverage GitLab MCP server with 44 tools across 18 resource types. Agent-optimized CQRS design — one tool call handles complete multi-step operations. Supports OAuth 2.1, read-only mode, stdio/SSE/StreamableHTTP transports, and GraphQL-native work items with full hierarchy (epics,issues,etc)1,922 npm8Apache 2.0
- FlicenseNot gradedqualityCmaintenanceUnified MCP server for Git forge management across GitHub, GitLab, Gitea, and Bitbucket, enabling repository, issue, PR, and CI/CD operations via CLI tools and APIs.-
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for GitLab — exposes 1006 GitLab REST & GraphQL API operations as MCP tools (42 meta-tools / 57 enterprise), 24 resources, 38 prompts, and 17 completion types for AI assistants. Written in Go, single static binary, stdio and HTTP transport.249MIT
- AlicenseBqualityDmaintenanceThe most comprehensive Azure DevOps MCP server & CLI — 13 tools, 82 actions, single Go binary.141Apache 2.0

FluxGit MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceFluxGit gives Codex, Claude Code, OpenCode and compatible MCP clients shared Git context through 38 tools: 25 read tools, 12 operation-preview tools and cancellation. Previews submit proposals; approval and execution require a connected FluxGit desktop gateway and a person's decision. Available workflows depend on the client and configuration.Apache 2.0
TDQS
Scored across 78 tools
Most tools are scoped by resource and action, but several pairs overlap enough to cause misselection: project_get vs project_resolve, auth vs user_me, mr_cancel vs mr_close, and issue_close vs issue_edit with status CLOSED. Descriptions help clarify some cases, but the boundaries are not consistently crisp.
All tools use snake_case with the gitflic_ prefix, and most follow a predictable resource_action pattern such as gitflic_mr_create or gitflic_issue_comment. Minor deviations like gitflic_auth, gitflic_user_me, gitflic_project_list_my, and gitflic_mr_by_commit keep it from being fully consistent.
With 78 tools, the surface is far larger than the recommended 3-15 range and is heavy for an agent to navigate reliably. The domain is broad and the tools are grouped by resource, but many CRUD/auth variants could be consolidated or exposed more selectively.
Coverage is strong across projects, merge requests, issues, comments, branches, tags, releases, commits, webhooks, users, and authentication. Some expected lifecycle operations are missing or partial, such as project delete, tag delete, webhook edit, and MR reviewer assignment, but most core workflows are supported.