Introducing Source Code Connect your repository and scan any branch, commit, or tag for actionable source code findings. Try it now

Product

Introducing the Ostorlab Platform MCP Server

Ostorlab now supports MCP, giving AI assistants and agents permission-controlled access to security data and workflows.

Introducing the Ostorlab Platform MCP Server

Thu 06 August 2026

Ostorlab now supports MCP through the Ostorlab Platform MCP Server, giving AI assistants and agents a direct, permission-controlled way to work with security data and workflows in your Ostorlab organisation.

This means an MCP-capable AI client can work with scans, vulnerabilities, remediation tickets, assets, integrations, automation, and reports. You can ask it to inspect what needs attention in a scan, find vulnerabilities that still need remediation, create tickets, check connected integrations, or start another scan.

For example, ask an agent to summarize a scan and identify what needs attention, and it can pull the scan data, inspect the vulnerabilities, group them by severity, and surface the relevant findings.

Ostorlab MCP agent querying and analyzing scan data

The agent queries Ostorlab directly and identifies the findings that need attention.

What is MCP?

MCP, or Model Context Protocol, is a standard that allows AI assistants and agents to connect to external systems and use their tools. Instead of navigating a UI or manually constructing API calls, an MCP-capable client can call defined tools and receive structured results.

With the Ostorlab Platform MCP Server, those tools connect to your Ostorlab organisation. The AI can work with the security context already available in the platform and, when permitted, take the next action without requiring that information to be manually moved into the conversation.

Organisation-level access control

Access to the Ostorlab MCP Server is controlled through an organisation API key. Every tool checks the permissions associated with that key before performing an operation:

  • READ — inspect data.
  • WRITE — create or change data.
  • ADMIN — perform privileged operations, such as reading the organisation audit log.

Access to scans and vulnerabilities is scoped further, so an API key only sees the specific objects it has been granted access to. Secret material such as passwords, tokens, API keys, OAuth secrets, and webhook URLs is not returned through MCP.

This is our first step in bringing Ostorlab security workflows directly to MCP-capable AI assistants and agents. We’d love to hear how you use it, what workflows you build around it, and what you would like the Ostorlab Platform MCP Server to support next.

Have ideas, feedback, or a workflow you’d like to see supported? Give us your feedback →

Table of Contents