About Cobaltstrike MCP Server
Cobaltstrike MCP Server is an MCP server published by Cobalt-Strike in the Developer Tools category: mCP Server for Cobalt Strike interaction. It has been installed 0 times through Conduid.
The repository has 12 stars and 3 forks, with the last commit 8 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx cobaltstrike-mcp-serverThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Cobaltstrike MCP Server
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Cobalt Strike MCP Server
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 😉
Getting Started
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.
Prerequisites
- Python 3.8+ installed
- FastMCP 2.12.5 or higher
- The Cobalt Strike API Server should be running.
- Cobalt Strike should be installed and configured.
- Cobalt Strike should be properly licensed
Installation
-
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
Alternative: System-wide Installation
pip install -r requirements.txt
Configuration
Environment Variables
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
.env File Support
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
Viewing Environment Variables
Use the --show-env option to see all supported environment variables and their current values:
python cs_mcp.py --show-env
This displays:
- All supported environment variables
- Current values (SET/NOT SET)
- Description and default values
- No authentication required
Command Line Arguments
The following parameters can be used while starting the MCP Server:
Cobalt Strike API
--base-url: Base URL for the Cobalt Strike REST API (https://<CS_HOST>:50443)
Authentication
--username: Cobalt Strike username (required)--password: Cobalt Strike password (required)--duration-ms: JWT session duration in milliseconds
HTTP Client
--http-timeout: HTTP request timeout in seconds--insecure: Disable TLS certificate verification--verify-tls: Enable TLS certificate verification
MCP Server
--transport: MCP transport protocol (http, streamable-http, sse, stdio)--listen-host: Host interface to bind the server to--listen-port: Port to bind the server to--listen-path: URL path for the MCP endpoint--server-name: Name displayed to MCP clients--instructions: Instructions for MCP clients
Advanced
--log-level: Override uvicorn log level for HTTP transport--experimental-openapi-parser: Enable FastMCP's experimental OpenAPI parser (default: enabled)--no-experimental-openapi-parser: Disable the experimental OpenAPI parser
Basic Usage
The MCP Server can be run standalone from the command line.
# Activate virtual environment first
source venv/bin/activate # or venv\Scripts\activate on Windows
# Start the MCP server with command line arguments
python cs_mcp.py --username your_username --password your_password --insecure
Using Environment Variables
# Set credentials via environment variables
export CS_API_USERNAME="rest_client"
export CS_API_PASSWORD="CobaltStrikePassword"
export CS_API_VERIFY_TLS="false"
# Run with minimal command line arguments
python cs_mcp.py
Using .env File
# Create and edit .env file
cp .env.example .env
# Edit .env with your credentials
# Run
python cs_mcp.py --transport stdio
Available Tools
The MCP server automatically exposes all Cobalt Strike REST API endpoints as tools. Some key categories include:
Beacon Management
listBeacons: Get all active beaconsgetBeacon: Get specific beacon informationremoveBeacon: Remove a beacon- [...]
Commands
executeShell: Execute shell commands on beaconsexecuteSleep: Change beacon sleep intervalsexecuteUpload: Upload files to target systemsexecuteDownload: Download files from target systems- [...]
Payloads
generatePayload: Generate various payload typeslistPayloads: Get available payload options- [...]
Listeners
createListener: Create new listenerslistListeners: Get active listenersremoveListener: Remove listeners- [...]
MCP Prompts
The server includes built-in MCP example prompts to help operation planning.
MCP Resources
The server exposes static Cobalt Strike data through MCP resources:
[!NOTE] Resources provide read-only access to live Cobalt Strike data and are automatically updated.
Claude Desktop Integration
-
Copy the configuration example:
cp claude_desktop_config_example.json ~/.config/claude-desktop/claude_desktop_config.json -
Edit the configuration:
- Set your Cobalt Strike credentials
- Adjust the server URL and ports as needed
{ "mcpServers": { "Cobalt Strike MCP": { "name": "Cobalt Strike MCP", "command": "<PROJECT LOCATION>/venv/Scripts/python.exe", "args": [ "<PROJECT LOCATION>\\cs_mcp.py" ], "env": { "CS_API_BASE_URL": "https://localhost:50443", "CS_API_USERNAME": "resp_api_user", "CS_API_PASSWORD": "CobaltStrikePassword", "CS_API_VERIFY_TLS": "false", "MCP_TRANSPORT": "stdio" } } } } -
Restart Claude Desktop to load the new configuration.
Troubleshooting
Common Issues
-
Authentication Failed
RuntimeError: Authentication failed with status 401 or 403- Verify your username and password
- Ensure the user has API access permissions
- Check that the Cobalt Strike team server is running
-
Connection Refused
httpx.ConnectError: [Errno 61] Connection refused- Verify the base URL and port
- Ensure the team server's REST API is enabled
- Check firewall settings
-
TLS Certificate Errors
httpx.HTTPStatusError: SSL: CERTIFICATE_VERIFY_FAILED- Use
--insecureflag for self-signed certificates - Or install the proper CA certificate and use
--verify-tls
- Use
-
Import Errors
ModuleNotFoundError: No module named 'fastmcp'- Ensure virtual environment is activated
- Run
pip install -r requirements.txt
Support
For issues and questions:
- Check the troubleshooting section above
- Review Cobalt Strike documentation for API requirements
- Consult FastMCP documentation for MCP-specific issues
[!WARNING] This tool provides direct access to Cobalt Strike capabilities, which include powerful adversary simulation capabilities. Use responsibly and only in environments where you have explicit permission to perform security testing.
README mirrored from the source repository 3 months ago. The original is authoritative.