Stackhawk MCP Server

An MCP server that provides interaction with StackHawk's security scanning platform. Exposed over MCP by the stackhawk mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server for integrating with StackHawk's security scanning platform. Helps developers set up StackHawk, run security scans, and triage findings to fix vulnerabilities — all from within an LLM-powered IDE or chat.

• Setup: — Detect your project, create a StackHawk application, and generate a ready-to-scan stackhawk.yml
• Scan: — Run StackHawk scans directly from your IDE or chat (with install help if the CLI is missing)
• Triage: — Get actionable findings at or above your failure threshold for remediation
• Validate: — Check YAML configs against the official schema and validate field paths to prevent hallucination
• Custom User-Agent: — All API calls include a versioned User-Agent header

Adding it to your client

stackhawk-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• Phase — Tool
• Discover — get_organization_info
• Setup — setup_stackhawk_for_project
• Validate — validate_stackhawk_config
• Scan — run_stackhawk_scan
• Triage — get_app_findings_for_triage

Configuration

You will need 2 environment variables: STACKHAWK_API_KEY, COPILOT_MCP_STACKHAWK_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the stackhawk mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Stackhawk's toolset — Phase, Discover, Setup and 3 more — is a fair guide to whether it matches your workflow. It is maintained by com.stackhawk; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.