Adaptixc2 MCP Server

AdaptixC2 MCP服务器

______________________________________________________________________

✨ 概述

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

它允许人工智能驱动的红队、开发后任务的自动化以及C2环境中受控的工具执行。

AdaptixC2 MCP AdaptixC2 MCP AdaptixC2 MCP

______________________________________________________________________

🚀 安装和设置

Python 3.10+和 uv 包管理器(curl -LsSf https://astral.sh/uv/install.sh | sh)是必需的。

1. 克隆存储库：

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

1. 创建隔离的虚拟环境并安装依赖项：

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

1. 配置连接参数：

复制配置模板，并使用您的详细信息（IP、端口、C2凭据、端点）对其进行编辑：

cp .env.example .env

______________________________________________________________________

🤖 连接到LLM

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

示例：Gemini CLI

创建配置文件：

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

Gemini CLI的配置示例：

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

______________________________________________________________________

🛡️ BOF集成（可选）

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

1.构建和安装扩展工具包

从官方克隆和编译模块 扩展套件 存储库：

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

2.在AdaptixC2中配置profile.yaml

在 profile.yaml AdaptixC2 Teamserver的配置文件，您必须从第一步开始指定编译文件的路径（使用绝对路径很重要）：

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

有关主C2服务器的更多详细信息： AdaptixC2文档

3.通过bofs.yaml限制人工智能访问

为了最大限度地降低风险并避免过度的工具暴露，服务器强制执行严格的 默认拒绝 BOF模块的模型。

编辑 bofs.yaml 根目录中的文件 AdaptixC2 MCP Server。您必须明确列出允许AI使用的命令：

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

# Or allowing the entire category
ADCS-BOF: all 

*如果一个类别被注释掉，或者配置被完全注释掉，则不会加载BOF工具。*

______________________________________________________________________

内置工具（无需BOF）

• agent_info
• change_directory
• copy_file
• 下载文件
• execute_powershell
• execute_raw
• execute_shell
• get_downloaded_file
• 获取ID
• get_working_directory
• jobs_kill
• jobs_list
• kill-agent
• kill过程
• 列表_代理
• list_credentials
• adaptix\_\_list_directory
• list_disks
• list_downloads
• list_listeners
• 列表_流程
• list_targets
• list_task_历史
• list_tunnels
• 日志查找
• make_directory
• move_file
• 港口向前
• adaptix\_\_read_file
• remove_file
• 反向前进
• run_process
• save_writeup
• set_agent_sleep
• 启动锁4
• 启动锁5
• 停止隧道
• tag_agent
• view_session_notes

基于BOF的工具

• bof_adbof
• bof_adcsbf
• bof_credsbof
• bof_elevationbof
• bof执行
• bof_injectonbof
• bof_kbeusbo
• bof_侧向运动
• bof_dapbof
• bof_msqlbof
• bof_postxbof
• bof_processbof
• bof回放信息
• bof_albof
• 转炉渣

提示

1） 本地特权升级

You are an experienced red team operator performing post-exploitation in a controlled lab environment.

MCP server are already connected and available to you.
You must use these MCP capabilities to execute commands on the compromised host.

Key Architecture Fact:
Each bof_* tool is a GROUP containing many subcommands, not a single action. Always read the tool's full description to see ALL available subcommands before deciding what to run.

Operational Logic:
NEVER skip recon. Always follow a logical sequence:
1. Establish current context (who you are, network position, system details)
2. Determine whether the host is domain-joined using available system information
3. If the host is domain-joined:
   - Perform domain-aware enumeration where relevant
4. If the host is NOT domain-joined:
   - Completely ignore domain-related actions
5. Identify privilege escalation vectors through local enumeration
6. Escalate privileges → continue enumeration

Critical Rules:
- Never assume environment context (domain vs non-domain) without verifying it first
- All argument values must come from prior recon, not guesses
- Validate each step before proceeding
- When unsure which subcommand to use, read the full tool description

You already have access to a compromised Windows host.

Your objective:
- Escalate privileges to local administrator on the current machine

IMPORTANT:
- After successful privilege escalation, you MUST spawn a new agent with elevated (administrator/SYSTEM) privileges

Path to agent:
C:\Users\Username\Downloads\agent.exe

Focus only on local privilege escalation to gain privileged access.

⚠️ 免责声明

本项目仅用于授权的安全测试和研究目的。

请勿在您不拥有或没有明确测试权限的系统上使用此软件。