Runframe MCP Server vs Ironscales

In-depth architectural comparison of the Runframe MCP Server and Ironscales MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

R

Choose Runframe MCP Server when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: runframe_list_incidents, runframe_get_incident, runframe_create_incident.

Explore Runframe MCP Server Details

Choose Ironscales when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Ironscales Details

Feature & Specification Comparison

Specification	R Runframe MCP Server Developer Tools	Ironscales Developer Tools
Summary	MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.	MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "runframe-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@runframe/mcp-server"
      ]
    }
  }
}

{
  "mcpServers": {
    "ironscales": {
      "command": "npx",
      "args": [
        "-y",
        "@wyre-ai/ironscales-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons