Dradis MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRADIS_URL | Yes | Your Dradis instance URL | |
| DRADIS_API_TOKEN | Yes | Your Dradis API token | |
| DRADIS_DEFAULT_TEAM_ID | No | Default team ID for project creation (optional) | |
| DRADIS_DEFAULT_TEMPLATE_ID | No | Default template ID for project creation (optional) | |
| DRADIS_VULNERABILITY_PARAMETERS | No | Comma-separated list of vulnerability field names (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setProjectA | Set the current Dradis project context for all subsequent operations |
| getProjectDetailsA | Get detailed information about the current Dradis project including metadata, team, and settings |
| createProjectB | Create a new Dradis project with specified configuration and automatically set it as the current project context |
| createVulnerabilityA | Create a new security vulnerability finding in the current project with detailed information |
| getVulnerabilitiesA | Retrieve a paginated list of vulnerability summaries from the current project, including ID, title, and risk rating |
| getAllVulnerabilityDetailsB | Retrieve a paginated list of complete vulnerability details including all fields and metadata from the current project |
| getVulnerabilityB | Retrieve complete details for a specific vulnerability including all fields, evidence, and metadata |
| updateVulnerabilityA | Update an existing vulnerability with new information, modifying only the specified fields |
| getContentBlocksA | Retrieve all content blocks from the current project, including their IDs and field data |
| updateContentBlockA | Update a content block in the current project with new field values and content |
| getDocumentPropertiesA | Retrieve all document properties and their values for the current project configuration |
| upsertDocumentPropertyB | Create a new document property or update an existing property value in the current project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.