Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.steadwing.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What is the Steadwing MCP server?

The Steadwing MCP server brings AI-powered root cause analysis directly into your IDE. Ask your AI assistant to investigate a production error, and Steadwing returns the root cause with a suggested fix, no context switching or browser tabs required.

Root Cause Analysis

Trigger full RCA on errors, alerts, or stack traces from your IDE

Context-Aware

Leverages your connected integrations for deeper insights

File Analysis

Pass relevant source files for more accurate results

Zero Context Switch

Stay in your editor while Steadwing investigates

​
Setup

Get your API key from app.steadwing.com/organization.

​
Installation

Add to your project’s .cursor/mcp.json:
{
  "mcpServers": {
    "steadwing": {
      "command": "npx",
      "args": ["-y", "@steadwing/mcp-server"],
      "env": {
        "STEADWING_API_KEY": "your_api_key_here"
      }
    }
  }
}
Or install via the Cursor Marketplace (search “Steadwing”).

​
Tool: run_rca

The MCP server exposes a single tool run_rca that analyzes errors with AI-powered root cause analysis. Input:
ParameterRequiredDescription
errorYesError message, stack trace, or incident description
filesNoArray of { name, content } for relevant source files (max 20)
Output: A URL to the incident on Steadwing where you can view the full analysis.
Including relevant source files is strongly recommended for more accurate analysis. Start with files mentioned in the stack trace, then add related imports and configuration files.

​
How do I use the MCP server for debugging?

​
Investigating a Production Error

You’re debugging an issue and have a stack trace. Instead of manually searching logs and code: 
"Hey, investigate this error: ConnectionTimeout in PaymentService.processOrder()"
Steadwing automatically:
  • Searches your connected observability tools for related errors
  • Correlates with recent code changes in GitHub
  • Identifies the likely root cause
  • Suggests a fix

​
Analyzing Suspicious Code

You’re reviewing code and something looks off: 
"Investigate why this function might be causing memory leaks"
Steadwing examines the code pattern, checks for similar issues in your codebase, and explains potential problems with actionable recommendations.

​
Understanding an Alert

An alert fires and you want quick context: 
"What's causing the high latency alerts on the checkout service?"
Steadwing pulls metrics, recent deployments, and error patterns to give you a complete picture without leaving your editor.

​
How do integrations enhance MCP server results?

The MCP server works best when your Steadwing account has integrations connected:
IntegrationWhat It Adds
GitHubRepository context, recent commits, deployment history
Datadog / GrafanaMetrics, monitors, and APM data
SentryError tracking and stack traces
AWS / GCPCloud resource and service insights
Connect integrations at app.steadwing.com/settings to unlock full investigation capabilities.

​
FAQs

Yes, authentication is required. The MCP server connects to your Steadwing account to access your organization’s integrations and provide accurate analysis. Sign up at app.steadwing.com if you don’t have an account.
You can trigger root cause analysis on errors, stack traces, or alerts. Pass relevant source files alongside the error for more accurate results.
The MCP server requires authentication and works best with integrations. Without integrations, investigation capabilities are limited to local code analysis.
Cursor and Claude Desktop have the best MCP support. Any MCP-compatible client will work, check Smithery for the latest compatibility.
Only relevant file snippets you explicitly pass (via the files parameter) are sent for analysis. Review our privacy policy at steadwing.com for details.
Need help? Contact us at hello@steadwing.com