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

MCP serverRussian stack

cli-gitflic.ru/mcp-server.htmlAuthor:Тихон Устинов

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/gitflic-cli-mcp-server

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio --env 'GITFLIC_TOKEN=<your GITFLIC_TOKEN>' gitflic -- npx -y gitflic-cli-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"gitflic","type":"stdio","command":"npx","args":["-y","gitflic-cli-mcp"],"env":{"GITFLIC_TOKEN":"<your GITFLIC_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "gitflic": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add gitflic --env 'GITFLIC_TOKEN=<your GITFLIC_TOKEN>' -- npx -y gitflic-cli-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.gitflic]
command = "npx"
args = ["-y", "gitflic-cli-mcp"]
env = { GITFLIC_TOKEN = "<your GITFLIC_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "gitflic": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "gitflic-cli-mcp"
      ],
      "environment": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "gitflic": {
      "command": "npx",
      "args": [
        "-y",
        "gitflic-cli-mcp"
      ],
      "env": {
        "GITFLIC_TOKEN": "<your GITFLIC_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITFLIC_TOKENsecret, required
GITFLIC_MCP_GROUPSoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked on Sep 25, 2026.

Text for your agent

Get a personal GitFlic token in account settings and register the server with claude mcp add gitflic --env GITFLIC_TOKEN=<token> -- npx -y gitflic-cli-mcp, narrowing the tool set with GITFLIC_MCP_GROUPS, for example mr,issue, if needed.

Other ways from the author

claude mcp add gitflic --env GITFLIC_TOKEN=xxxx -- npx -y gitflic-cli-mcp

Command from the README; replace the token with your own GitFlic personal token.

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 comment

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.

MCP

Transport: stdio
Authentication: API key

Environment variables
Environment variables
GITFLIC_TOKEN required, 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

Security check

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

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.

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.

Superpowers

Editors’ pick

A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review

PluginMedium riskNo VPN needed292.5K

Skills for real engineers by Matt Pocock

Skills For Real Engineers

Editors’ pick

Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture

SkillLow risk271.4K

Spec Kit

Editors’ pick

GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation

CLIMedium riskNo VPN needed139.3K

Reference MCP servers

Model Context Protocol servers

Official

Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything

MCP serverMedium risk90.6K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Superpowers

Skills for real engineers by Matt Pocock

Spec Kit

Reference MCP servers