GitFlic MCP built on gitflic-cli
gitflic-cli MCP-сервер
An MCP server with 76 typed tools over a GitFlic CLI: merge requests, issues, releases, package registry, with group filters and a read-only mode
Extended access
Why this level
- It can create, edit and merge merge requests, issues and releases
- GITFLIC_MCP_NO_DESTRUCTIVE removes only deletion; other mutations remain available
- The token grants access to every project the token owner can reach
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/gitflic-cli-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- It can create, edit and merge merge requests, issues and releases
- GITFLIC_MCP_NO_DESTRUCTIVE removes only deletion; other mutations remain available
- The token grants access to every project the token owner can reach
This is third-party code. Review the repository files before installing.
What it does
The gitflic-cli-mcp package wraps the gitflic-cli CLI and maps its subcommands one to one into 76 typed stdio MCP tools for GitFlic, a Russian code-hosting platform. Tools are grouped by entity: merge requests, issues, branches, commits, blobs, projects, releases, tags, users and webhooks, with a mix of read and write operations. The set can be narrowed with environment variables: GITFLIC_MCP_GROUPS keeps only the needed groups, GITFLIC_MCP_READONLY strips all mutating tools, GITFLIC_MCP_NO_DESTRUCTIVE removes only the seven delete operations while keeping create and edit, and GITFLIC_MCP_TOOLS plus GITFLIC_MCP_EXCLUDE give a precise allowlist and denylist. The server also compresses GitFlic's raw REST responses, stripping noise like HAL wrappers and avatar URLs so the model's context is not wasted on it.
Who it is for. For developers who host code on GitFlic and want to manage merge requests, issues and releases straight from an agent.
Good fit when
- The repository lives on GitFlic, not GitHub or GitLab
- You want a narrow tool set for a task, for example only merge requests and issues
- You need the model to never see delete operations without explicit opt-in
Not a fit when
- Your code is on GitHub or GitLab: this server is GitFlic-only
- You need GitFlic's own official self-hosted admin tool: that is a separate vendor utility
Example request
Show open merge requests in my GitFlic project and create an issue from the first review commentMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
GITFLIC_TOKENrequired, secret- GitFlic personal access token
GITFLIC_API_BASE- API address for a self-hosted GitFlic instance, if not using gitflic.ru
GITFLIC_MCP_GROUPS- Comma-separated tool groups to keep, for example mr,issue
GITFLIC_MCP_READONLY- Set to 1 to keep only non-mutating tools
Limitations
The project is small and little-known: a single author, minimal outside feedback. All 76 tools go to the host via tools/list by default, a real context cost if the set is not narrowed with environment variables. Self-hosted GitFlic needs a separate GITFLIC_API_BASE setting. The claimed '100% REST API coverage' and tool count have not been independently verified.
How to disable. Remove the server with claude mcp remove gitflic, or delete the gitflic block from your client config.
FAQ
Do I need to install gitflic-cli separately?
No, npx pulls both gitflic-cli-mcp and its gitflic-cli dependency automatically.
How do I stop the model from deleting anything?
Set GITFLIC_MCP_NO_DESTRUCTIVE=1: the seven delete tools disappear from the list at registration time, not just behind a host confirmation prompt.
Discussion
No questions or reviews yet.
Related
MCP serversGitFlic MCP: 66 API tools
gitflic-mcp
The only MCP server found for GitFlic, a Russian repository-hosting platform: projects, issues, merge requests, files, releases, webhooks and CI/CD
A git MCP server with 28 tools: an agent clones, commits, branches, merges, rebases and manages worktrees in local repositories.
An MCP server for GitLab and self-hosted instances: projects, merge requests, issues, pipelines, wiki and releases
Official GitKraken MCP server from the gk CLI: git, pull requests and issues across GitHub, GitLab, Bitbucket and Jira
GitVerse MCP: code review and PRs
GitVerse MCP Server
A GitVerse MCP server with 25 bitbucket-mcp-style tools: pull requests, inline code review with verdicts and running GitVerse Actions CI pipelines
A remote MCP server that gives the agent docs and code of any public GitHub repository with nothing to install
README in short
The Russian README explains the MCP server is a thin layer over the CLI: each tool maps to a gitflic subcommand. It shows launching via npx with a token in GITFLIC_TOKEN, config examples for Claude Code and Cursor, a table of tool groups with read and write counts, the precedence order of the GROUPS, READONLY, NO_DESTRUCTIVE and TOOLS/EXCLUDE filters, the list of seven delete tools, and a section on compressing GitFlic's raw REST responses to save tokens.