Introducing Heeler MCP: Bring Security Context Directly Into Your AI-Powered Development Workflow

We're excited to announce Heeler MCP, a new way to access Heeler directly from your AI assistant or coding agent using the Model Context Protocol (MCP).
May 28, 2026

Security teams have spent years trying to bring developers closer to security. Yet most security tooling still requires engineers to leave their workflow, switch contexts, and navigate dashboards to find the answers they need.

Today, we're changing that.

We're excited to announce Heeler MCP, a new way to access Heeler directly from your AI assistant or coding agent using the Model Context Protocol (MCP).

Whether you're using Claude Desktop, Cursor, Windsurf, Zed, or any MCP-compatible AI assistant, Heeler can now provide security context directly inside the tools where developers already work.

No dashboard hunting. No copy-pasting findings. No context switching.

Just ask questions in natural language and get answers grounded in your organization's actual security data.

Security Context Where Development Happens

At Heeler, we've always believed that security teams don't need more findings—they need more context.

The challenge isn't generating alerts. It's helping developers and security teams understand which findings matter, where they exist, what they're impacting, and what should be fixed first.

With Heeler MCP, that context becomes available directly within AI-assisted workflows.

Developers can ask:

  • "What security issues exist in this repository?"
  • "What's the worst dependency vulnerability in this service?"
  • "Are there any SAST findings for the file I have open?"
  • "How is this application deployed, and is it internet-facing?"

The assistant automatically invokes the appropriate Heeler tools, retrieves real security data, and returns actionable answers without requiring the user to leave their editor.

From Security Dashboard to Conversational Security Platform

Heeler MCP exposes Heeler's security intelligence as a set of MCP tools that AI assistants can access on demand.

This enables entirely new workflows across application security, vulnerability management, and software risk analysis.

Find and Prioritize Findings Faster

Instead of digging through dashboards and filters, teams can simply ask:

"Show me all critical findings with fixes available in the payments service."

Or:

"Which findings are currently overdue on their SLO?"

Heeler understands organizational context—including repositories, teams, services, and applications—allowing users to search security data using natural language.

Understand Vulnerability Impact Instantly

When a new CVE is disclosed, security teams often spend hours determining exposure.

With Heeler MCP, questions become conversational:

"Where does CVE-2024-1234 affect us?"

"Which services are exposed to this vulnerability?"

"Is this vulnerability fixed everywhere in our environment?"

The assistant can immediately identify affected repositories, services, deployments, and open findings.

Prioritize Remediation by Impact

One of the biggest challenges in vulnerability management is determining what to fix first.

Rather than addressing findings individually, Heeler can identify remediation actions that eliminate the greatest amount of risk with the least effort.

Ask:

"What's the highest-impact package upgrade we can make right now?"

Or:

"Give me a prioritized fix plan for the auth-service."

Heeler ranks remediation opportunities based on their impact across your environment.

Bringing Runtime Context Into AI-Assisted Development

Traditional security tooling often stops at the code repository.

Heeler connects findings to deployments, services, exposure, ownership, and runtime context.

This means developers can ask questions such as:

"Is this service internet-facing?"

"What deployment exposure impact does this change create?"

"Does this repository have unresolved critical vulnerabilities?"

The answers are grounded in how software actually exists in production—not just what's visible in source code.

This is another step toward our broader vision of making security context available throughout the software lifecycle.

Security Reviews That Happen Before the Pull Request

Alongside MCP tooling, Heeler includes a set of reusable security prompts that help teams standardize secure development workflows.

Examples include:

Secure Development Checklist

Generate repository-aware security reviews based on the authentication patterns and architecture already present in your codebase.

Secure Code Risk Review

Review proposed code changes for common vulnerability classes including:

  • IDOR
  • XSS
  • SQL Injection
  • SSRF
  • Command Injection
  • Path Traversal
  • CSRF

SAST Pass

Surface existing SAST findings associated with changed files before code is committed.

Dependency Guard

Evaluate dependency risk and recommend upgrade paths before software ships.

Together, these workflows transform security reviews from a reactive activity into a proactive part of development.

Built for the Modern Engineering Stack

Heeler MCP supports repositories across:

  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps

It works with leading MCP-compatible AI assistants including:

  • Claude Desktop
  • Cursor
  • Windsurf
  • Zed
  • Compatible VS Code extensions
  • Other MCP clients

Editor-based clients automatically provide repository and file context, enabling security analysis without manual scoping.

For chat-based interfaces, users can simply provide a repository URL and Heeler handles the rest.

Get Started

Heeler MCP is available today.

If you're already using Heeler, you can connect your preferred MCP-compatible AI assistant and begin querying your security data immediately.

If you're new to Heeler, reach out to schedule a demo!

What’s new on Heeler
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Related resources

See All Resources