Vectra AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VECTRA_BASE_URL | Yes | Your Vectra portal URL | |
| VECTRA_MCP_HOST | No | Host to bind to for HTTP transports | 0.0.0.0 |
| VECTRA_MCP_PORT | No | Port for HTTP transports | 8000 |
| VECTRA_CLIENT_ID | Yes | Your client ID from Vectra | |
| VECTRA_MCP_DEBUG | No | Enable debug logging | false |
| VECTRA_CLIENT_SECRET | Yes | Your client secret from Vectra | |
| VECTRA_MCP_TRANSPORT | No | Transport protocol (stdio, sse, or streamable-http) | stdio |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_detection_idsC | |
| list_detections_with_basic_infoB | |
| list_detections_with_detailsB | |
| list_entity_detectionsC | |
| get_detection_countC | |
| get_detection_detailsC | |
| get_detection_summaryB | |
| get_detection_pcapC | |
| list_entitiesC | |
| lookup_entity_info_by_nameB | |
| lookup_host_by_ipA | |
| get_host_detailsB | |
| get_account_detailsB | |
| create_assignmentC | |
| list_assignmentsC | |
| list_assignments_for_userC | |
| delete_assignmentA | |
| get_assignment_detail_by_idB | |
| get_assignment_for_entityC | |
| create_entity_noteC | |
| mark_detection_fixedB | |
| list_platform_usersC | |
| list_lockdown_entitiesB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Summarize Detection | Get a detailed summary of a specific detection in Vectra AI platform. |
| Visualize Entity Detections | Visualize realtionship of detections related to a specific entity in Vectra AI platform with a interactive graph. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools have distinct purposes, but there is some overlap that could cause confusion. For example, list_detection_ids, list_detections_with_basic_info, and list_detections_with_details all serve similar functions with varying detail levels, which might lead to misselection. However, descriptions help clarify differences, and other tools like create_assignment or get_detection_pcap are clearly unique.
Tool names follow a consistent verb_noun pattern throughout, such as create_assignment, get_account_details, list_detections_with_details, and mark_detection_fixed. All tools use snake_case, and verbs like create, get, list, delete, and mark are applied predictably across different nouns, making the set easy to navigate.
With 23 tools, the count is borderline high for the security investigation domain, potentially feeling heavy. While the tools cover various aspects like assignments, detections, entities, and users, some could be consolidated (e.g., multiple detection listing tools) to reduce complexity without losing functionality.
The tool set provides comprehensive coverage for security investigation workflows, including CRUD operations for assignments and notes, detailed retrieval for accounts, hosts, and detections, and listing functions with filtering. Minor gaps exist, such as no tools for updating assignments or managing users beyond listing, but agents can likely work around these with the available tools.