MCP Server for Cobalt Strike interaction.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"cobaltstrike-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This is a PoC MCP server developed as part of some internal experiments during the development of CS 4.12 and the CS REST API. More information can be found here.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
An evil MCP server used for redteam testing
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
mcpki-server is the backend infrastructure for https://www.mcpki.org, enabling secure public key management and autonomous certificate handling for large language models (LLMs).
MCP Security Weekly
Get CVE alerts and security updates for Cobaltstrike Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This is a PoC MCP server developed as part of some internal experiments during the development of CS 4.12 and the CS REST API. More information can be found here.
https://github.com/user-attachments/assets/92d15b5f-4744-41aa-a803-abe342db8075
[!NOTE] This tool is still in early development stage and subject to breaking changes. It has been heavily vibe-coded, so don't be too hard on the quality of the code 😉
This MCP server provides a bridge between large language models like Claude and the Cobalt Strike C2 framework. It allows AI assistants to dynamically access and control the Cobalt Strike functionality through standardized tools, enabling a natural language interface to adversary simulation workflows.
Clone the repository
git clone <repository-url>
cd cobaltstrike-mcp-server
Create and activate a virtual environment
Windows:
setup.bat
venv\Scripts\activate
macOS/Linux:
setup.sh
source venv/bin/activate
Install dependencies
pip install -r requirements.txt
Verify Installation
python cs_mcp.py --help
pip install -r requirements.txt
You can configure the server using environment variables:
# Cobalt Strike API Configuration
export CS_API_BASE_URL="https://your-teamserver:50443"
export CS_API_USERNAME="your_username"
export CS_API_PASSWORD="your_password"
export CS_API_VERIFY_TLS="false" # Set to "true" for production
export CS_API_HTTP_TIMEOUT="30.0"
# MCP Server Configuration
export MCP_LISTEN_HOST="127.0.0.1"
export MCP_LISTEN_PORT="3000"
export MCP_TRANSPORT="http"
export MCP_SERVER_NAME="Cobalt Strike MCP"
# Logging
export LOG_LEVEL="INFO" # DEBUG, INFO, WARNING, ERROR
The server automatically loads environment variables from a .env file in the current directory if it exists:
Copy the example file:
cp .env.example .env
Edit the configuration:
# Edit .env with your settings
CS_API_USERNAME=rest_client
CS_API_PASSWORD=SecurePassword123
CS_API_VERIFY_TLS=false
MCP_TRANSPORT=stdio
Run without command line arguments:
python cs_mcp.py
Use the --show-env option to see all supported environment variables and their current values:
python cs_mcp.py --show-env
This displays:
The following parameters can be used while starting the MCP Server:
--base-url: Base URL for the Cobalt Strike REST API (https://<CS_HOST>:50443)--username: Cobalt Strike username (required)--password: Cobalt Strike password (required)--duration-ms: JWT session duration in milliseconds--http-timeout: HTTP request timeout in seconds--insecure: Disable TLS certificate verification--verify-tls: Enable TLS certificate v