GitFlic 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
- 0 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- It can create and delete projects, releases and webhooks, and trigger or cancel CI/CD pipelines
- The access token grants full project access under the rights of the user who created it
Install
- Works in
- Services
Manual install
git clone https://gitflic.ru/project/sazonovfm/gitflic-mcp.git && cd gitflic-mcp && npm install && npm run buildInstall from source; there is no published npm package.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- It can create and delete projects, releases and webhooks, and trigger or cancel CI/CD pipelines
- The access token grants full project access under the rights of the user who created it
This is third-party code. Review the repository files before installing.
What it does
The server covers 66 tools out of 182 documented GitFlic API endpoints, 13 categories including users, projects, issues with comments, repository files (reading up to 15 MB and a recursive listing), merge requests with code discussions, branches, commits, tags, releases, webhooks and CI/CD (pipelines, jobs, artifacts, CI/CD variables). It is built on TypeScript and the official MCP SDK with minimal dependencies, just the SDK and Zod. Some GitFlic API operations are not supported: for instance, branch DELETE returns 405 on api.gitflic.ru, and the server warns about this honestly rather than pretending the tool works.
Who it is for. For GitFlic teams who need agent access to projects, merge requests and CI/CD, with no market alternative.
Good fit when
- You want to manage GitFlic issues and merge requests from a chat with an agent
- You need to manage project releases, tags and webhooks
- You need to trigger and monitor GitFlic CI/CD pipelines
Not a fit when
- You need to delete a branch via the API: GitFlic returns 405, use a plain git push with a colon prefix instead
- You need CI/CD with no .gitflic-ci.yaml file of your own and a connected runner
Example request
Create a merge request from feature into main in myorg/backend and trigger a pipeline for itMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
GITFLIC_TOKENrequired, secret- GitFlic access token from settings, Settings, Access Tokens
GITFLIC_API_URL- API base URL, defaults to https://api.gitflic.ru
Limitations
It covers 66 of 182 documented endpoints, with some operations left out. Deleting branches via the API does not work on api.gitflic.ru (405 Method Not Allowed), a GitFlic limitation, not a server bug. CI/CD tools need a .gitflic-ci.yaml file in the repository and a connected runner; without them start_pipeline and related tools will not work.
How to disable. Remove the gitflic entry from your MCP client config and revoke the access token in GitFlic settings.
FAQ
Can this server delete a branch?
No, GitFlic's API returns 405 on branch DELETE; use git push origin :refs/heads/branch-name instead.
Are there alternatives for GitFlic?
The author states this is the only MCP server found specifically for GitFlic.
Discussion
No questions or reviews yet.
Related
MCP serversGitFlic 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
A git MCP server with 28 tools: an agent clones, commits, branches, merges, rebases and manages worktrees in local repositories.
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
An MCP server for GitLab and self-hosted instances: projects, merge requests, issues, pipelines, wiki and releases
A remote MCP server that gives the agent docs and code of any public GitHub repository with nothing to install
Official GitKraken MCP server from the gk CLI: git, pull requests and issues across GitHub, GitLab, Bitbucket and Jira
README in short
The README gives the motivation (the only server for GitFlic, 66 of 182 endpoints), source installation via npm, an environment variable table, very detailed documentation of every tool across 13 categories with parameters, known limitations (405 on branch delete, CI/CD requirements), and bilingual documentation (README.md and README.en.md).