---

✨ 概述

AdaptixC2 MCP 服务器使LLM代理能够通过MCP协议与AdaptixC2框架交互并自动化操作。

它允许AI驱动的红队化、利用后任务的自动化，以及在C2环境中实现受控工具执行。

---

🚀 安装与设置

Python 3.11+ 和 uv 包管理器（[curl -LsSf https://astral.sh/uv/install.sh | sh）是必备的。

1. 克隆仓库：

2. 创建一个隔离的虚拟环境并安装依赖：

3. 配置连接参数： 复制配置模板，并编辑你的详细信息（IP、端口、C2凭证、端点）：

---

🤖 连接大型语言模型

把服务器启动参数添加到你的MCP客户端配置中。

示例：Gemini CLI

创建配置文件：

Gemini CLI 的示例配置：

---

🛡️ BOF 集成（可选）

服务器支持 BOF。要激活此功能，Teamserver 和 MCP 双方都需要额外的设置步骤。

1.构建与安装扩展套件

从官方的 Extension-Kit 仓库中克隆并编译这些模块：

2.配置配置文件。

AdaptixC2 MCP Server

---

✨ Overview

AdaptixC2 MCP Server enables LLM agents to interact with and automate operations with the AdaptixC2 framework via the MCP protocol.

It allows AI-driven red teaming, automation of post-exploitation tasks, and controlled tool execution within a C2 environment.

---

🚀 Installation and Setup

Python 3.11+ and the uv package manager (curl -LsSf https://astral.sh/uv/install.sh | sh) are required.

1. Clone the repository:

git clone https://github.com/Faceless0x7/AdaptixC2-MCP-Server
cd AdaptixC2-MCP-Server

2. Create an isolated virtual environment and install dependencies:

uv venv
source .venv/bin/activate
uv pip install -r requirements.txt

3. Configure connection parameters: Copy the configuration template and edit it with your details (IP, port, C2 credentials, endpoint):

cp .env.example .env

---

🤖 Connecting to LLMs

Add the server startup parameters to your MCP client configuration.

Example: Gemini CLI

Create the configuration file:

mkdir -p .gemini
nano .gemini/settings.json

Example configuration for Gemini CLI:

{
  "mcpServers": {
    "adaptixc2": {
      "command": "uv",
      "args": [
        "--directory",
        "/home/kali/Desktop/AdaptixC2-MCP-Server",
        "run",
        "server.py"
      ]
    }
  }
}

---

🛡️ BOF Integration (Optional)

The server supports BOFs. To activate this functionality, additional setup steps are required on both the Teamserver and the MCP side.

1. Build and Install Extension-Kit

Clone and compile the modules from the official Extension-Kit repository:

git clone https://github.com/Adaptix-Framework/Extension-Kit
cd Extension-Kit
make

2. Configure profile.yaml in AdaptixC2

In the profile.yaml configuration file of your AdaptixC2 Teamserver, you must specify the path to the compiled file from the first step (it is important to use an absolute path):

axscripts:
  - "/full/path/to/Extension-Kit/extension-kit.axs"

For more details about the main C2 server: AdaptixC2 Documentation

3. Restricting AI Access via bofs.yaml

To minimize risk and avoid excessive tool exposure, the server enforces a strict default-deny allowlist for BOF modules.

Edit the bofs.yaml file in the root directory of AdaptixC2 MCP Server. You must explicitly list which commands the AI is allowed to leverage:

# Example: Granting access only to two required BOFs in AD
AD-BOF:
  - dcsync single
  - adwssearch

# Or allowing the entire category
ADCS-BOF: all 

Rules: