mirror of
https://github.com/Ed1s0nZ/CyberStrikeAI.git
synced 2026-03-31 00:09:29 +02:00
50 lines
2.2 KiB
Markdown
50 lines
2.2 KiB
Markdown
# MCP Servers
|
||
|
||
[中文](README_CN.md)
|
||
|
||
This directory contains **standalone MCP (Model Context Protocol) servers**. They speak the standard MCP protocol over stdio (or HTTP/SSE when a server supports it), so **any MCP client** can use them—not only CyberStrikeAI, but also **Cursor**, **VS Code** (with an MCP extension), **Claude Code**, and other clients that support MCP.
|
||
|
||
**We will keep adding useful MCP servers here.** New servers will cover security testing, automation, and integration scenarios. Stay tuned for updates.
|
||
|
||
## Available servers
|
||
|
||
| Server | Description |
|
||
|--------|-------------|
|
||
| [reverse_shell](reverse_shell/) | Reverse shell listener: start/stop listener, send commands to connected targets, full interactive workflow. |
|
||
|
||
## How to use
|
||
|
||
These MCPs are configured per client. Use **absolute paths** for `command` and `args` when using stdio.
|
||
|
||
### CyberStrikeAI
|
||
|
||
1. Open Web UI → **Settings** → **External MCP**.
|
||
2. Add a new external MCP and fill in the JSON config (see each server’s README for the exact config).
|
||
3. Save and click **Start**; the tools will appear in conversations.
|
||
|
||
### Cursor
|
||
|
||
Add the server to Cursor’s MCP config (e.g. **Settings → Tools & MCP → Add Custom MCP**, or edit `~/.cursor/mcp.json` / project `.cursor/mcp.json`). Example for a stdio server:
|
||
|
||
```json
|
||
{
|
||
"mcpServers": {
|
||
"reverse-shell": {
|
||
"command": "/absolute/path/to/venv/bin/python3",
|
||
"args": ["/absolute/path/to/CyberStrikeAI-main/mcp-servers/reverse_shell/mcp_reverse_shell.py"]
|
||
}
|
||
}
|
||
}
|
||
```
|
||
|
||
Replace the paths with your actual paths. Cursor will spawn the process and talk MCP over stdio.
|
||
|
||
### VS Code (MCP extension) / Claude Code / other clients
|
||
|
||
Configure the client to run the server via **stdio**: set the **command** to your Python executable and **args** to the script path (see each server’s README). The client will launch the process and communicate over stdin/stdout. Refer to your client’s docs for where to put the config (e.g. `.mcp.json`, `~/.claude.json`, or the extension’s settings).
|
||
|
||
## Requirements
|
||
|
||
- Python 3.10+ for Python-based servers.
|
||
- Use the project’s `venv` when possible: e.g. `venv/bin/python3` and the script under `mcp-servers/`.
|