Skip to content

Integrations Overview

middleBrick integrates into your workflow however you prefer to work, from a web dashboard for one-off scans to CI/CD automation that blocks insecure deploys.

IntegrationBest forPlan
DashboardVisual scans, exploring results, sharing reportsFree
REST APICustom integrations, scripts, internal toolingFree
CLITerminal workflows, CI scripts, quick local scansFree
MCP ServerAI-assisted security (Claude, Cursor, Windsurf)Starter
GitHub ActionPR checks, deploy gates, automated scanningPro
FeatureDashboardAPICLIMCPGitHub Action
Submit scanYesYesYesYesYes
View resultsYesYesYesYesYes
OpenAPI specYesYesYesYesYes
Context parameterYesYesYesYesYes
JSON outputYesYesYesYes
PDF exportYes
Score threshold gateYesYes
PR status checkYes
Conversational analysisYes
Scan historyYesYesYesYes
API key managementYes

Use the Dashboard. Sign up, paste a URL, see your results. No setup, no API key, no installation.

Install the CLI. npm install -g middlebrick, log in, scan. Pipe output to jq for scripting, use exit codes for CI gates.

Use the GitHub Action (Pro plan). Set a score threshold — if the API drops below it, the PR check fails. Add it to your existing workflow in 5 lines of YAML.

Use the REST API. Build scans into your internal tools, dashboards, Slack bots, or any system that can make HTTP requests.

”I want my AI assistant to scan for me”

Section titled “”I want my AI assistant to scan for me””

Set up the MCP Server (Starter plan). Claude, Cursor, and other MCP-compatible assistants can scan APIs, interpret results, and suggest fixes in natural language.

All integrations (except the Dashboard UI) authenticate with an API key:

Authorization: Bearer mb_your_api_key_here
  1. Go to your dashboard
  2. Click Generate API Key
  3. Copy the key (it’s only shown once)
  4. Store it securely (environment variable, GitHub Secret, etc.)

Keys are scoped to your account and inherit your plan’s rate limits and scan quotas. You can revoke a key at any time from the dashboard.

  • Never hardcode API keys in source code
  • Use environment variables or secret managers
  • Rotate keys regularly. Generate a new one, update your integrations, then revoke the old one.
  • Use separate keys for different environments (CI, staging, local) so you can revoke individually