cPanel MCP Server

add_directory_user

Add user credentials to a password-protected directory. Specify directory path, username, and password to control access for that user.

Instructions

Add a user to a password-protected directory

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dir": "<dir>",
      "user": "<user>",
      "password": "<password>"
    },
    "name": "add_directory_user"
  }
}

Input Schema

Name	Required	Description
`dir`	Yes	Directory path to protect
`user`	Yes	Username
`password`	Yes	Password

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior on its own. It only states the mutation action without covering side effects, permissions, reversibility, or what happens if the directory does not already have password protection. This is insufficient for a mutation tool.

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?

The description is a single sentence with no redundant words, front-loading the core purpose. It is concise and well-structured for a simple action.

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

Completeness2/5

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

With no output schema and no annotations, the description alone lacks important context such as preconditions (e.g., directory must already be protected), behavior on failure, and response format. It is minimal but not complete for a mutating tool.

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

Parameters3/5

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

Schema coverage is 100%, with each parameter already described ('Directory path to protect', 'Username', 'Password'). The description adds no additional parameter-level meaning beyond the schema, so the baseline 3 applies.

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 the action ('Add a user') and the resource ('password-protected directory'), making it distinct from sibling tools like list_directory_privacy and other user-management tools for databases or email.

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

Usage Guidelines3/5

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

The description implies usage for managing directory privacy but does not explicitly state when to use it versus alternatives or mention any prerequisites (e.g., the directory must already be protected). No when-not-to-use guidance is provided.

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

Deploy Server