Claude-C2 MCP server

Command and control framework that enables secure remote system administration through a Python server and PowerShell client, maintaining task tracking in SQLite for efficient execution and reporting.
Back to servers
Provider
dmcxblue
Release date
May 16, 2025
Language
Python
Stats
73 stars

This Python-based MCP server creates endpoints to manage tasks and output, allowing Claude to communicate with a C2 (Command & Control) server. It works with a PowerShell client that handles communication back to the C2 server, enabling seamless integration between Claude and your C2 infrastructure.

Installation & Setup

To get the MCP server running, follow these steps:

  1. Clone the repository to your local machine
  2. Install the required dependencies
  3. Configure the server
  4. Start the server

Prerequisites

  • Python 3.6 or higher
  • PowerShell (for the client component)
  • Network access between Claude, the MCP server, and your C2 server

Installing Dependencies

pip install flask requests

Usage

Starting the MCP Server

To start the server, run the Python script:

python mcp_server.py

By default, the server will listen on port 5000. You can modify this in the configuration file if needed.

Configuring Claude

To allow Claude to communicate with your MCP server, you'll need to provide Claude with the appropriate configuration. This includes:

  • The MCP server URL
  • Any authentication credentials required
  • Specific instructions for how to format requests

Using the PowerShell Client

The PowerShell client handles communication between your systems and the C2 server. Basic usage:

.\c2_client.ps1 -Server "http://your-mcp-server:5000" -Action "get_tasks"

Common Commands

Here are some common commands you can use with the system:

  • Get Tasks: Retrieve pending tasks from the C2 server
  • Submit Output: Send command output back to the C2 server
  • Check Status: Verify the connection status

Example Workflow

  1. Claude makes a request to the MCP server
  2. The MCP server processes the request and communicates with the C2 server
  3. The PowerShell client executes the required actions
  4. Results are sent back through the chain to Claude

Troubleshooting

Common Issues

  • Connection Refused: Ensure the MCP server is running and accessible
  • Authentication Errors: Verify your credentials are correctly configured
  • Timeout Errors: Check network connectivity between all components

Logs

Check the server logs for detailed information about any issues:

cat mcp_server.log

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later