Beagle Security MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEAGLE_SECURITY_API_TOKEN | Yes | Your Beagle Security API token (can be obtained from Profile → Personal access token in your Beagle Security account settings) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| beagle_create_projectC | Create a new project in Beagle Security |
| beagle_list_projectsC | List all projects and applications |
| beagle_modify_projectC | Modify an existing project |
| beagle_delete_projectC | Delete a project |
| beagle_create_applicationC | Create a new application in a project |
| beagle_get_applicationC | Get application details by token |
| beagle_modify_applicationC | Modify an existing application |
| beagle_list_applicationsC | List all applications under a project |
| beagle_delete_applicationC | Delete an application |
| beagle_get_domain_signatureC | Get domain verification signature |
| beagle_verify_domainC | Complete domain verification |
| beagle_start_testC | Start an automated penetration test |
| beagle_get_test_statusC | Get the status of a running test |
| beagle_stop_testC | Stop a running test |
| beagle_get_test_resultC | Get detailed test results in JSON format |
| beagle_list_test_sessionsC | List all test sessions for an application |
| beagle_list_running_testsC | List all running tests for user or team |
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 17 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (applications, projects, tests) and actions (create, delete, get, list, modify, start, stop, verify), making it easy for an agent to select the correct tool for any operation without confusion.
All tool names follow a consistent verb_noun pattern with the prefix 'beagle_'. This uniform naming convention (e.g., beagle_create_application, beagle_get_test_result) ensures predictability and readability throughout the tool set, with no deviations in style or structure.
With 17 tools, the server is well-scoped for its purpose of managing Beagle Security projects, applications, and tests. Each tool earns its place by covering essential operations like CRUD for projects and applications, test management, and domain verification, without being overly sparse or bloated.
The tool set provides complete CRUD/lifecycle coverage for the domain of security testing management. It includes creation, retrieval, listing, modification, and deletion for projects and applications, along with comprehensive test operations (start, stop, status, results, sessions) and domain verification, leaving no obvious gaps for agent workflows.