Dradis MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dradis MCP Create a new project named 'Security Audit'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dradis MCP
A FastMCP server implementation for interacting with Dradis Pro, a collaborative platform for information security teams. This MCP allows you to manage projects and vulnerabilities in Dradis directly through your MCP-enabled tools.
Features
Project Management
Create new projects
Get project details
Set active project for operations
Vulnerability Management
Create vulnerabilities
Update existing vulnerabilities
Get vulnerability details
Get all vulnerability details
List vulnerabilities with pagination support
Content Block Management
Get all content blocks in current project
Update a content block
Document Property Management
Get all document properties
Create or update a document property
Robust error handling and input validation
Consistent JSON response formatting
Related MCP server: mcp-defectdojo
Prerequisites
Node.js (v14 or higher)
npm
A Dradis Pro instance
Dradis API token
Installation
npm installConfiguration
Environment Variables
Create a .env file in the root directory with the following variables:
DRADIS_URL=<url>
DRADIS_API_TOKEN=<token>
DRADIS_DEFAULT_TEAM_ID=<teamId>
DRADIS_DEFAULT_TEMPLATE_ID=<templateId>
DRADIS_VULNERABILITY_PARAMETERS=<commaSeparatedParams> // Title,Description,Solution,etc. MCP Config File
To add Dradis MCP to your MCP configuration, add the following to your config file to mcp.json if you're using 5ire:
{
"servers": [
{
"key": "Dradis",
"command": "npx",
"description": "A Model Context Protocol server that provides integration with Dradis note-taking platform",
"args": ["-y", "dradis-mcp"],
"env": {
"DRADIS_URL": "<url:string:Your Dradis instance URL>",
"DRADIS_API_TOKEN": "<token:string:Your Dradis API token>",
"DRADIS_DEFAULT_TEAM_ID": "<number:string:Default team ID for project creation>",
"DRADIS_DEFAULT_TEMPLATE_ID": "<number:string:Default template ID for project creation>"
},
"isActive": false
}
]
}Available Tools
Project Management
setProject: Set the current Dradis project{ projectId: number }getProjectDetails: Get details of the current project// No parameters requiredcreateProject: Create a new Dradis project{ name: string; team_id?: number; // Optional if DRADIS_DEFAULT_TEAM_ID is set report_template_properties_id?: number; // Optional if DRADIS_DEFAULT_TEMPLATE_ID is set author_ids?: number[]; template?: string; // Optional if DRADIS_DEFAULT_TEMPLATE is set }
Vulnerability Management
createVulnerability: Create a new vulnerability{ text: string; // Content with #[ ]# field syntax }getVulnerabilities: List vulnerabilities (25 per page){ page?: number; // Optional page number }getVulnerability: Get specific vulnerability{ vulnerabilityId: number; }updateVulnerability: Update existing vulnerability{ issueId: number; parameters: { text: string; } }
Content Block Management
getContentBlocks: Get all content blocks in current project// No parameters requiredupdateContentBlock: Update a content block{ blockId: number; contentBlock: { content: string; } }
Document Property Management
getDocumentProperties: Get all document properties// No parameters requiredupsertDocumentProperty: Create or update a document property{ propertyName: string; value: string; }
Development
To run the server in development mode with the CLI:
npm run devTo inspect the server using MCP Inspector:
npm run inspectBuilding
To build the TypeScript code:
npm run buildRunning in Production
To run the built server:
npm startProject Structure
/src- Source codeapi.ts- Dradis API client implementationconfig.ts- Configuration loading and validationserver.ts- MCP server implementationtypes.ts- TypeScript type definitions
/dist- Compiled JavaScript (generated after build)
Error Handling
The MCP provides detailed error messages for:
Missing or invalid configuration
API request failures
Invalid input parameters
Missing project ID
Network errors
Response Format
All tool responses are formatted as JSON with consistent structure:
Success responses include relevant data and optional success messages
Error responses include detailed error messages and context
List endpoints include pagination metadata when applicable
Available Tools
12 toolscreateProjectB
Create a new Dradis project with specified configuration and automatically set it as the current project context
Inputs: name (required), team_id (required), template, author_ids, +1 more.
createVulnerabilityA
Create a new security vulnerability finding in the current project with detailed information
getAllVulnerabilityDetailsB
Retrieve a paginated list of complete vulnerability details including all fields and metadata from the current project
Inputs: page, filterByRisk.
getContentBlocksA
Retrieve all content blocks from the current project, including their IDs and field data
Inputs: blockGroup, includeContent.
getDocumentPropertiesA
Retrieve all document properties and their values for the current project configuration
Inputs: includeEmpty, propertyPrefix.
getProjectDetailsA
Get detailed information about the current Dradis project including metadata, team, and settings
Inputs: includeMetadata.
getVulnerabilitiesA
Retrieve a paginated list of vulnerability summaries from the current project, including ID, title, and risk rating
Inputs: page, includeFields.
getVulnerabilityB
Retrieve complete details for a specific vulnerability including all fields, evidence, and metadata
Inputs: vulnerabilityId (required), includeEvidence.
setProjectA
Set the current Dradis project context for all subsequent operations
Inputs: projectId (required).
updateContentBlockA
Update a content block in the current project with new field values and content
Inputs: blockId (required), contentBlock (required).
updateVulnerabilityA
Update an existing vulnerability with new information, modifying only the specified fields
Inputs: issueId (required), parameters (required).
upsertDocumentPropertyB
Create a new document property or update an existing property value in the current project
Inputs: value (required), propertyName (required), overwriteExisting.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Most tools target distinct resources and actions, but getVulnerabilities and getAllVulnerabilityDetails both return paginated vulnerability lists and could be confused despite one providing summaries and the other full details. Other tools are clearly separated by resource type.
All tool names follow a consistent verb_noun camelCase pattern (e.g., setProject, getVulnerability, updateContentBlock). The use of 'upsert' is a common and clear convention, so there are no naming style inconsistencies.
With 12 tools, the server is well-scoped for managing Dradis projects, vulnerabilities, content blocks, and document properties. Each tool has a clear role and the count is neither overwhelming nor too sparse.
The tool surface covers create/read/update for vulnerabilities and projects, and read/update for content blocks and document properties, but lacks delete operations entirely. Also missing are project listing and content block creation, which are notable gaps for full lifecycle management.
Related MCP Connectors
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
Generate PDF, Word (.docx) and PowerPoint (.pptx) documents from Markdown over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes the pentest reporting and automation features of SysReptor as programmable tools for AI agents and automated workflows. It enables users to manage findings, projects, and templates through a standardized interface by wrapping the reptor CLI.13MIT
- AlicenseAqualityDmaintenanceMCP server for DefectDojo vulnerability management, exposing 24 tools for managing products, engagements, tests, findings, scan imports, and finding lifecycle through the Model Context Protocol.241MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Metasploit Framework via the msfrpc protocol, exposing tools for module management, session control, and exploitation through MCP.79 PyPI1MIT
- AlicenseAqualityBmaintenanceEnables querying the WPScan API for WordPress plugin, theme, core vulnerabilities, and specific vulnerability lookups through MCP tools.4287 npmMIT