Bright's Model Context Protocol (MCP) integration brings AI-powered application security testing directly into your development workflow. Your AI coding assistant can discover API endpoints, run security scans, and review vulnerabilities — all through natural language conversation.
Bright MCP is a remote, cloud-hosted MCP server. There is nothing to install locally — you simply point your MCP-compatible client at Bright's endpoint and authenticate with an API key.
Quick Start
1. Get a Bright API Key
Create a dedicated API key in your Bright account. This can be a personal, project, or organization-level key with the relevant scopes. See Personal API Key Scopes for details.
2. Configure Your Client
Add Bright as a remote MCP server in your IDE or tool of choice. The server URL is:
https://app.brightsec.com/mcp
Note: If your organization uses a dedicated Bright cluster, replace app.brightsec.com with your cluster's hostname.
Any MCP-compatible client that supports remote HTTP/SSE servers can connect to Bright. Configure it with:
Setting
Value
Transport
SSE (Server-Sent Events) or HTTP
URL
https://app.brightsec.com/mcp
Auth Header
Authorization: Api-Key YOUR_KEY
Available Tools
Bright MCP exposes the following tools to your AI assistant:
Project Management
Tool
Description
listProjects
List all projects accessible to your API key. Use this to find project IDs needed for other operations.
Endpoint Discovery
Tool
Description
runDiscovery
Discover API endpoints using crawling (crawlerUrls) or API definitions (fileId from uploadApiDefinition). Before running, check if the project already has entrypoints with listEntrypoints. For private/local targets, specify a connected repeater via repeaters.
getDiscoveryStatus
Get the current status of a discovery run.
listDiscoveries
List discovery history for a project. View past discovery runs or monitor ongoing endpoint discovery.
uploadApiDefinition
Upload an API definition file (OpenAPI/Swagger) by URL or content. Returns a file ID to reference in discovery runs.
Entrypoint Management
Tool
Description
listEntrypoints
List discovered API endpoints/URLs for a project. Use this to select entrypoints for scans or evaluate attack surface coverage. Supports filtering by HTTP method, status, and text search.
getEntrypoint
Get detailed information about a specific entrypoint by ID, including headers, body, and configuration.
addEntrypoint
Add a new entrypoint to a project. Entrypoints define HTTP requests (method, URL, headers, body) that can be used for security scanning.
editEntrypoint
Update an existing entrypoint. Modify the HTTP request definition, authentication, or repeater settings.
Security Scanning
Tool
Description
runScan
Start a security scan against selected entrypoints. Supports targeting specific entrypoints by ID or by status (e.g., new, changed, vulnerable). Configure which tests to run or use a scan template. For private/local targets, specify a connected repeater.
getScanStatus
Get the current status of a running scan.
listScans
List scan history for a project. View past scan results or check the status of multiple ongoing scans.
listTests
List all available security tests (e.g., SQL injection, XSS, CSRF) that can be included in scans.
Vulnerability Management
Tool
Description
listIssues
List security vulnerabilities found for a project. Filter by severity (Low, Medium, High, Critical), status (new, recurring, resolved, ignored), or entrypoint.
Authentication Configuration
Tool
Description
listAuths
List authentication configurations for a project. Use before scanning protected endpoints that require authentication.
getAuth
Get detailed information about a specific authentication configuration.
addAuth
Create a new authentication configuration. Supports multiple auth types: static headers, OAuth 2.0/OIDC, multi-step HTTP flows, NTLM, browser-based login, and recorded browser flows.
editAuth
Update an existing authentication configuration.
Private/Local Target Access
Tool
Description
createRepeater
Create a repeater for accessing private/local targets. After creation, run the Bright CLI to start the repeater and establish the connection.
listRepeaters
List repeaters and their connection status. Verify a repeater is connected before scanning non-public applications.
Your AI assistant connects to Bright's MCP endpoint over SSE/HTTP.
Bright's cloud platform receives tool calls and orchestrates security operations.
Scans run against your application — either directly (public targets) or through a Repeater (private/local targets).
Repeaters (Private/Local Targets)
To scan applications that aren't publicly accessible, Bright uses Repeaters — lightweight agents that route scan traffic from Bright's cloud through your local network.
Create a repeater via the MCP tool (createRepeater)
This repository contains configuration examples and documentation for Bright's MCP integration. Bright's security scanning platform is a commercial SaaS product — visit brightsec.com for more information.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Bright Security?
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Bright Security einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.