Skip to main content

Overview

The MCP (Model Context Protocol) integration brings Steadwing’s powerful RCA and code analysis capabilities directly into your development environment. Work with your local codebase in popular IDEs and AI coding tools like Claude Code, Cursor, and other MCP-compatible tools without switching contexts.

Why Use MCP with Steadwing?

IDE Integration

Access Steadwing directly in Claude Code, Cursor, and other MCP-enabled tools

Local Code Analysis

Work with your local codebase without requiring GitHub authentication

Enhanced Performance

Connect integrations for faster analysis and deeper insights

Seamless Workflow

Stay in your development environment while performing RCA

Benefits

  • No GitHub Required to Start - Begin analyzing code immediately with local access
  • Universal IDE Support - Works with any MCP-compatible development tool
  • Optional Integration Boost - Connect GitHub and observability tools for enhanced performance
  • Real-time Analysis - Get instant feedback without leaving your editor
  • Context-Aware Assistance - Steadwing understands your local development context

Setup Instructions

Step 1: Install MCP Server from Smithery

  1. Visit the Steadwing MCP Server on Smithery
  2. Follow the installation instructions for your specific IDE or tool
  3. The MCP server will be configured automatically

Step 2: Authenticate with Steadwing (Required for Claude Code)

Claude Code Users: After installation, you must manually authenticate with Steadwing to use the MCP server.
  1. After installing the MCP server in Claude Code, you’ll need to authenticate
  2. Follow the authentication prompts in your IDE
  3. Sign in with your Steadwing account at app.steadwing.com
  4. Once authenticated, you can start using Steadwing with your local code
Authentication ensures secure access to Steadwing’s analysis capabilities and allows the MCP server to leverage your connected integrations.

Step 3: Start Using with Local Code

Once authenticated, the MCP integration allows you to:
  • Analyze local code files directly from your IDE
  • Perform root cause analysis on local changes
  • Get code suggestions based on your development context
  • Access Steadwing capabilities without leaving your editor

Step 4: Connect Integrations for Enhanced Performance (Optional)

For significantly improved performance and deeper insights:
  1. Navigate to Steadwing Integrations
  2. Connect your preferred integrations:
    • GitHub - For repository-wide analysis and deployment tracking
    • Sentry - For error and exception correlation
    • Datadog - For metrics and performance data
    • New Relic - For application performance monitoring
    • Slack - For collaborative incident response
Connecting these integrations enables:
  • Faster analysis with full repository context
  • Correlation with production metrics and errors
  • Access to deployment history
  • Enhanced solution proposals based on complete system state

Supported Development Tools

The Steadwing MCP server works with popular development environments, including:
  • Claude Code - Anthropic’s AI coding assistant
  • Cursor - AI-first code editor
  • Any MCP-compatible IDE - Growing ecosystem of supported tools

How MCP Integration Works

Local Analysis Mode

When using MCP without connected integrations:
  1. Steadwing accesses your local codebase through the IDE
  2. Analyzes files and changes in your working directory
  3. Provides suggestions based on local context
  4. No external authentication required

Enhanced Mode with Integrations

When integrations are connected:
  1. Local code analysis is combined with repository data
  2. Production metrics and errors are correlated with code changes
  3. Deployment history provides additional context
  4. Analysis speed and accuracy are significantly improved

Configuration

MCP Server Settings

The MCP server is configured automatically during installation. Advanced configuration options may be available depending on your IDE.

Integration Connection

To connect integrations for enhanced performance:
  1. Sign up at app.steadwing.com
  2. Navigate to Integrations
  3. Follow the setup instructions for each integration
  4. The MCP server will automatically use connected integrations

FAQs

Yes, Claude Code users must authenticate with Steadwing after installing the MCP server. This authentication is done through your Steadwing account (not GitHub). Once authenticated, you can start analyzing your local code. Optionally, connecting GitHub and other integrations significantly improves performance and provides deeper insights.
Without integrations, MCP works with your local code only. With integrations connected, you get enhanced performance, access to production metrics, error correlation, deployment history, and repository-wide analysis.
The Steadwing MCP server works with any MCP-compatible development tool, including Claude Code, Cursor, and other emerging MCP-enabled environments. Check the Smithery installation page for the latest compatibility information.
Visit app.steadwing.com/integrations and follow the setup instructions for each integration you want to connect. The MCP server will automatically leverage these integrations once connected.
Yes, you can use both the MCP integration in your IDE and the web interface at app.steadwing.com. They share the same integrations and data when you’re signed in.
The MCP server processes code according to your IDE’s privacy settings and MCP protocol specifications. When integrations are connected, relevant context may be analyzed to provide better insights. Review the privacy policy at steadwing.com for details.
Need additional help? Please reach out to us at [email protected]