Fix security findings in your repository using a coding agent and verify the fixes on your live site.
Also known as GuardBee/guardbee-mcp, @guardbee/mcp-security-engineer
- Stars
- 2
- Tools
- 6
- Downloads, 30 days
- 903
- Latest version
- 0.2.0
- Last commit
- Nov 12, 2026
- License
- MIT
What is GuardBee Security Engineer MCP?
GuardBee Security Engineer is an MCP server. Fix security findings in your repository using a coding agent and verify the fixes on your live site. It exposes 6 tools, such as list_assessments, get_assessment, detect_stack.
Summary generated from the project's README
About GuardBee Security Engineer MCP server
Remediating security vulnerabilities in your codebase by connecting GuardBee AI findings directly to your coding agent is what this server enables. Developers using Claude Code, Cursor, or VS Code can pull actionable security assessments into their local environment to address issues identified by GuardBee. The server provides tools to list recent assessments, detect your technology stack including Next.js, Express, Nginx, Apache, or Cloudflare, and retrieve specific code fixes.
To use this server, you must provide a GuardBee API key with remediations.read and remediations.write scopes. The server operates locally through your agent, meaning it never edits your code or servers directly; instead, it provides the necessary diffs and fixes for your agent to implement and for you to approve. Once you deploy your changes, you can use the verify_fix tool to re-run checks against your live site to ensure the vulnerability is gone.
What you can do with it
- 1Remediate security vulnerabilitiesAsk your coding agent to fix the most urgent security findings from your latest GuardBee assessment.
- 2Identify technology stacksHave the agent automatically detect if your repository uses Nginx, Apache, or Next.js to find relevant configuration files.
- 3Verify live site securityConfirm that a security patch is working correctly by re-running the original check against your deployed website.
- 4Track applied fixesRecord the specific commit SHA or pull request URL once a security fix has been implemented in your repository.
Written from the project's README. Every use case is checked against a quote from it.
How to install GuardBee Security Engineer MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall GuardBee Security Engineer MCP in Claude Code
$ claude mcp add --env 'GUARDBEE_API_KEY=<YOUR_GUARDBEE_API_KEY>' security-engineer -- npx -y @guardbee/mcp-security-engineerInstall GuardBee Security Engineer MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"security-engineer": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-security-engineer"
],
"env": {
"GUARDBEE_API_KEY": "<YOUR_GUARDBEE_API_KEY>"
}
}
}
}Install GuardBee Security Engineer MCP in VS Code
.vscode/mcp.json
{
"servers": {
"security-engineer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-security-engineer"
],
"env": {
"GUARDBEE_API_KEY": "<YOUR_GUARDBEE_API_KEY>"
}
}
}
}Install GuardBee Security Engineer MCP in VS Code CLI
$ code --add-mcp '{"name":"security-engineer","type":"stdio","command":"npx","args":["-y","@guardbee/mcp-security-engineer"],"env":{"GUARDBEE_API_KEY":"<YOUR_GUARDBEE_API_KEY>"}}'Install GuardBee Security Engineer MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"security-engineer": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-security-engineer"
],
"env": {
"GUARDBEE_API_KEY": "<YOUR_GUARDBEE_API_KEY>"
}
}
}
}Install GuardBee Security Engineer MCP in Codex
$ codex mcp add security-engineer --env 'GUARDBEE_API_KEY=<YOUR_GUARDBEE_API_KEY>' -- npx -y @guardbee/mcp-security-engineerInstall GuardBee Security Engineer MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.security-engineer] command = "npx" args = ["-y", "@guardbee/mcp-security-engineer"] [mcp_servers.security-engineer.env] GUARDBEE_API_KEY = "<YOUR_GUARDBEE_API_KEY>"
Install GuardBee Security Engineer MCP in Gemini CLI
$ gemini mcp add -s user -e 'GUARDBEE_API_KEY=<YOUR_GUARDBEE_API_KEY>' security-engineer npx -- -y @guardbee/mcp-security-engineerInstall GuardBee Security Engineer MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"security-engineer": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-security-engineer"
],
"env": {
"GUARDBEE_API_KEY": "<YOUR_GUARDBEE_API_KEY>"
}
}
}
}GuardBee Security Engineer MCP tools 6
Detected from the READMElist_assessmentsget_assessmentdetect_stackget_fixreport_appliedverify_fix
| list_assessments | β | |
| get_assessment | β | |
| detect_stack | β | |
| get_fix | β | |
| report_applied | β | |
| verify_fix | β |
Configuration
GUARDBEE_API_KEYRequiredSecretGuardBee API key with remediations.read and remediations.write scopes
| Name | Description | |
|---|---|---|
| GUARDBEE_API_KEY | GuardBee API key with remediations.read and remediations.write scopes | RequiredSecret |
Automated checks
Ran Nov 12, 2026Full report βPassed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@guardbee/mcp-security-engineer
π¬π§ English | πΉπ· TΓΌrkΓ§e
Fix GuardBee AI Security Engineer findings in your own repository with your coding agent (Claude Code, Cursor, VS Code), then verify the fix on the live site.
GuardBee finds and explains the issue and proposes a fix for your platform. Your coding agent makes the change in your repository, and you approve it. GuardBee never edits your code or servers.
Telemetry is off by default. With
GUARDBEE_TELEMETRY=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
Tools
| Tool | What it does |
|---|---|
list_assessments |
Recent AI Security Engineer assessments of your workspace |
get_assessment |
Actionable findings, highest priority first, with the platforms each can be fixed on |
detect_stack |
Detects Next.js, Express, Nginx, Apache or Cloudflare from your repository's files (including vercel.json, netlify.toml, public/_headers, and Dockerfiles that reference nginx), notes Fly/Firebase hosting when present, and finds config files to diff against |
get_fix |
A reviewable fix for a finding. If you pass your Nginx or Apache config, you get an exact diff. |
report_applied |
Records that the fix was applied, with the commit SHA or PR URL as a reference |
verify_fix |
After you deploy, re-runs the check that reported the finding against the live site |
Setup
- In GuardBee, open Developers β API keys and create a key with the
remediations.readandremediations.writescopes. - Add the server to your agent.
Claude Code
claude mcp add guardbee-security-engineer -e GUARDBEE_API_KEY=gb_... -- npx -y @guardbee/mcp-security-engineer
Cursor / VS Code (mcp.json)
{
"mcpServers": {
"guardbee-security-engineer": {
"command": "npx",
"args": ["-y", "@guardbee/mcp-security-engineer"],
"env": { "GUARDBEE_API_KEY": "gb_..." }
}
}
}
Example
"Fix the top GuardBee findings of my latest assessment in this repo."
The agent:
- Calls
list_assessmentsand thenget_assessment. - Calls
detect_stack. For example, it finds Next.js anddeploy/nginx.conf. - Calls
get_fixfor each finding, editsnext.config.jsor the Nginx config, and shows you the diff. - After you approve and commit, calls
report_appliedwith the commit SHA. - After you deploy, calls
verify_fix, and GuardBee confirms the issue is resolved.
Configuration
| Variable | Default |
|---|---|
GUARDBEE_API_KEY |
required |
GUARDBEE_BASE_URL |
https://app.guardbee.ai |
GUARDBEE_TELEMETRY |
off; 1 turns on anonymous usage telemetry |
Security
- The server only reads files inside the project root, and only the config file you name. Paths outside the root are rejected.
- File edits are made by your agent, and you approve them there.
- All actions are recorded in the GuardBee activity log, marked as coming from an MCP client.
License
MIT
GuardBee Security Engineer MCP questions
How do I add GuardBee Security Engineer MCP to Claude Code?
Run claude mcp add --env 'GUARDBEE_API_KEY=<YOUR_GUARDBEE_API_KEY>' security-engineer -- npx -y @guardbee/mcp-security-engineer in your terminal. Add --scope user to make it available in every project.
How do I add GuardBee Security Engineer MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does GuardBee Security Engineer MCP provide?
It exposes 6 tools, including list_assessments, get_assessment, detect_stack, get_fix, report_applied.
Does GuardBee edit my code directly?
No, GuardBee never edits your code or servers; your coding agent makes the changes in your repository and you approve them.
What technologies can the server detect?
The server can detect Next.js, Express, Nginx, Apache, or Cloudflare from your repository files.
Is telemetry enabled by default?
No, telemetry is turned off by default and must be explicitly enabled using the GUARDBEE_TELEMETRY variable.