Cursor Configuration for CyberStrikeAI HTTP Mode: Complete Setup Guide

Configure Cursor for CyberStrikeAI HTTP mode by creating a .cursor/mcp.json file in your project root with an mcpServers entry that sets transport to "http" and url to the MCP endpoint, typically http://127.0.0.1:8081/mcp.

CyberStrikeAI exposes its Model Context Protocol (MCP) endpoint over HTTP, allowing the Cursor IDE to communicate directly with the AI service. The Cursor configuration for CyberStrikeAI HTTP mode requires a specific JSON configuration file that defines the transport protocol and server URL. According to the Ed1s0nZ/CyberStrikeAI source code, this setup enables AI agents to invoke tools and manage conversations through simple HTTP POST request/response semantics.

Understanding the MCP HTTP Transport

The Model Context Protocol (MCP) enables standardized communication between AI clients and servers. When using CyberStrikeAI in HTTP mode, Cursor communicates via standard HTTP POST requests rather than stdio or other transports. This requires setting the transport field to "http" in your configuration file.

The HTTP transport uses request/response semantics where Cursor sends tool invocation requests to the CyberStrikeAI server and receives structured responses. This mode is ideal for local development and team environments where multiple Cursor instances need to share the same AI backend.

Creating the .cursor/mcp.json Configuration File

Cursor reads MCP server definitions from a file named .cursor/mcp.json located at your project root. This file contains an mcpServers object where each key represents a named server configuration.

As documented in the README.md of the repository, the standard configuration looks like this:

{
  "mcpServers": {
    "cyberstrike-ai-http": {
      "transport": "http",
      "url": "http://127.0.0.1:8081/mcp"
    }
  }
}

The transport field specifies HTTP as the communication method, while url points to the MCP endpoint exposed by the CyberStrikeAI service. When this file is present, Cursor automatically detects the server in the Add Custom MCP → HTTP UI.

Configuring the CyberStrikeAI MCP Server

Before Cursor can connect, you must enable the HTTP MCP server within CyberStrikeAI itself. This is controlled in the config.yaml file at the repository root.

According to the source code in [config.yaml](https://github.com/Ed1s0nZ/CyberStrikeAI/blob/main/config.yaml#L94-L98), the MCP server configuration resides under the mcp block:

mcp:
  enabled: true
  port: 8081
  host: 0.0.0.0

Setting enabled to true starts the HTTP server on the specified port and host. The default configuration binds to 0.0.0.0:8081, making the endpoint accessible at http://127.0.0.1:8081/mcp on the local machine.

Customizing Host and Port Settings

If you run CyberStrikeAI on a different host or port, update both config.yaml and .cursor/mcp.json to match. For remote deployments, specify the full hostname in the URL field.

To connect to a remote CyberStrikeAI instance, modify your .cursor/mcp.json as follows:

{
  "mcpServers": {
    "cyberstrike-ai-remote": {
      "transport": "http",
      "url": "http://my-server.example.com:8081/mcp"
    }
  }
}

Ensure your firewall and network configuration allow HTTP traffic between Cursor and the CyberStrikeAI host. The transport value remains "http" regardless of whether you use localhost or a remote server.

Activating the Configuration in Cursor

Once you have created .cursor/mcp.json and started the CyberStrikeAI service, open your project in Cursor. Navigate to Settings → External MCP → Add Custom MCP → HTTP, and the cyberstrike-ai-http entry appears in the server list.

Selecting this entry allows the AI agent to invoke tools, retrieve knowledge bases, and manage conversation contexts through the HTTP transport. Commit the .cursor/mcp.json file to version control to share the Cursor configuration for CyberStrikeAI HTTP mode with your team.

Summary

• Create a .cursor/mcp.json file in your project root to define the HTTP MCP connection
• Set transport to "http" and url to http://127.0.0.1:8081/mcp for default local setups
• Enable the HTTP server in CyberStrikeAI via the mcp block in config.yaml
• Customize the host and port in both files for remote or non-standard deployments
• Cursor automatically detects the server in the Add Custom MCP HTTP UI when the configuration file is present

Frequently Asked Questions

What is the default port for CyberStrikeAI HTTP mode?

The default port is 8081, as defined in the mcp section of config.yaml. The server binds to host 0.0.0.0 by default, making it accessible via http://127.0.0.1:8081/mcp on the local machine.

Where do I place the Cursor MCP configuration file?

Place the .cursor/mcp.json file in your project root directory. Cursor automatically scans for this file when loading a workspace and populates the External MCP settings with any defined HTTP servers.

Can I use a remote host instead of localhost?

Yes. Change the url field in .cursor/mcp.json to point to your remote CyberStrikeAI instance, such as http://my-server.example.com:8081/mcp. Ensure the transport remains set to "http" and that network connectivity exists between Cursor and the remote host.

How do I enable the MCP HTTP server in CyberStrikeAI?

Set mcp.enabled to true in your config.yaml file. This starts the HTTP MCP server on the configured port, allowing Cursor to connect via the HTTP transport protocol defined in your .cursor/mcp.json file.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}