Skip to main content
Glama
wagonbomb

Megaraptor MCP

by wagonbomb
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

deploy_server_docker

Deploy a Velociraptor server using Docker for digital forensics and incident response. Configure deployment profiles, ports, and resource limits to launch an operational server.

Instructions

Deploy Velociraptor server using Docker (fastest method).

Optimized for rapid incident response. Server will be operational within 2-5 minutes.

Args: profile: Deployment profile ('rapid', 'standard', 'enterprise') server_hostname: Hostname for server access gui_port: GUI/API port (default 8889) frontend_port: Client connection port (default 8000) memory_limit: Container memory limit (default 4g) cpu_limit: Container CPU limit (default 2)

Returns: Deployment details including URLs and one-time admin password.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNorapid
server_hostnameNolocalhost
gui_portNo
frontend_portNo
memory_limitNo4g
cpu_limitNo2

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/megaraptor_mcp/tools/deployment.py:183-214 (handler)
    The implementation of the `deploy_server_docker` tool, which registers as an MCP tool and delegates the actual deployment logic to `deploy_server` with `deployment_type="docker"`.
    @mcp.tool()
async def deploy_server_docker(
    profile: str = "rapid",
    server_hostname: str = "localhost",
    gui_port: int = 8889,
    frontend_port: int = 8000,
    memory_limit: str = "4g",
    cpu_limit: str = "2",
) -> list[TextContent]:
    """Deploy Velociraptor server using Docker (fastest method).

    Optimized for rapid incident response. Server will be operational
    within 2-5 minutes.

    Args:
        profile: Deployment profile ('rapid', 'standard', 'enterprise')
        server_hostname: Hostname for server access
        gui_port: GUI/API port (default 8889)
        frontend_port: Client connection port (default 8000)
        memory_limit: Container memory limit (default 4g)
        cpu_limit: Container CPU limit (default 2)

    Returns:
        Deployment details including URLs and one-time admin password.
    """
    return await deploy_server(
        deployment_type="docker",
        profile=profile,
        server_hostname=server_hostname,
        gui_port=gui_port,
        frontend_port=frontend_port,
    )

Tool Definition Quality

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses timing ('operational within 2-5 minutes') and return values ('URLs and one-time admin password'). However, it omits safety details like idempotency, failure modes, whether existing deployments are overwritten, or cleanup requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections: purpose statement, timing estimate, Args block with param details, and Returns block. No redundant or filler text; every sentence adds specific operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of server deployment and presence of output schema, the description adequately covers operational parameters and return values. Minor gap: lacks mention of infrastructure prerequisites or reference to destroy_deployment for cleanup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage (only titles). The description fully compensates by documenting all 6 parameters with semantics, including enum values for 'profile' ('rapid', 'standard', 'enterprise') and default value indicators, exceeding what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states specific action ('Deploy Velociraptor server'), method ('using Docker'), and differentiates from siblings ('fastest method'). The incident response context further clarifies the operational intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage context ('Optimized for rapid incident response', 'fastest method') suggesting when to choose this over alternatives. However, it does not explicitly name sibling tools like deploy_server or deploy_server_cloud as alternatives, nor does it state prerequisites (e.g., Docker installation required).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wagonbomb/megaraptor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server