Skip to main content
Glama

add_hub_server

Register an external MCP server (Docker, local command, or SSE) to the hub for tool discovery and execution in security workflows.

Instructions

Add a new MCP server to the hub.

Register a new external MCP server that can be used for tool discovery and execution. Servers can be Docker images, local commands, or SSE endpoints.

:param name: Unique name for the server (e.g., "nmap", "nuclei"). :param server_type: Connection type ("docker", "command", or "sse"). :param image: Docker image name (for docker type). :param command: Command and args (for command type). :param url: SSE endpoint URL (for sse type). :param category: Category for grouping (e.g., "reconnaissance"). :param description: Human-readable description. :param capabilities: Docker capabilities to add (e.g., ["NET_RAW"]). :param environment: Environment variables to pass. :return: Information about the added server.

Examples:

  • Docker: add_hub_server("nmap", "docker", image="nmap-mcp:latest", capabilities=["NET_RAW"])

  • Command: add_hub_server("custom", "command", command=["python", "server.py"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
server_typeYes
imageNo
commandNo
urlNo
categoryNo
descriptionNo
capabilitiesNo
environmentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries burden. It describes server types and parameters but lacks details on side effects, authorization, or return format beyond a vague 'Information about the added server'. Adequate but not rich.

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

Conciseness4/5

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

Well-structured with a one-liner, explanation, parameter list, and examples. Slightly verbose but front-loaded and every sentence adds value.

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 output schema existence and 9 parameters, the description covers all params, includes examples, and mentions return value. Missing details on behavioral specifics like error handling.

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?

With 0% schema coverage, the description compensates fully by listing and explaining all 9 parameters with examples, adding significant meaning beyond the schema's raw types.

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?

The description clearly states 'Add a new MCP server to the hub' and explains the action with examples. It distinguishes from siblings like 'start_hub_server' and 'list_hub_servers' by focusing on registration.

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?

The description explains when to use the tool (to register servers) and includes server types and examples. However, it does not explicitly state when not to use it or compare to alternatives like 'start_hub_server'.

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/FuzzingLabs/secpipe'

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