Skip to main content
Glama
iMateo

fastpanel-mcp

by iMateo

site_create

Create a website on FastPanel with domain, IPs, and PHP version. Optionally create owner, database, and FTP accounts. Run dry_run first, then confirm to apply.

Instructions

Create a new website in FastPanel using the /api/master wizard endpoint. Can create owner/database/FTP inline atomically. Does NOT issue SSL — call certificate_create_letsencrypt after site is active. WRITE operation — set dry_run:true first, then confirm:true to execute. Flow: (1) POST /api/master/domain probes for existing email/DNS zones, (2) PUT /api/master creates the site with everything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipsYesServer IPs to bind to, e.g. ['100.42.181.157']. Get from sites_list → ips field.
domainYesPrimary domain, e.g. 'example.com' or 'sub.example.com'
aliasesNoAdditional domain aliases, e.g. ['www.example.com']
confirmNo
dry_runNo
handlerNoPHP handler: php_fpm is faster, fcgi simpler. Use site_get on existing sites to see what this project prefers.fcgi
databaseNoOptionally create a new database linked to this site. Omit to skip DB creation.
owner_idNoExisting FastPanel user id (from users_list). Use this OR new_owner, not both.
new_ownerNoCreate a new user inline. Use this OR owner_id, not both. EXPERIMENTAL — not yet tested against live API.
ftp_accountNoOptionally create an FTP account. Omit to skip.
php_versionYesPHP version without dot: 74=7.4, 80=8.0, 82=8.2, 83=8.3, 84=8.4
Behavior5/5

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

No annotations provided, so description carries full burden. It labels as WRITE operation, notes atomicity, flags new_owner as experimental, and states it does NOT issue SSL. This clearly discloses behavioral traits.

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 concise (four sentences), front-loaded with purpose, and logically structured: purpose, capabilities, exceptions, workflow. No superfluous words.

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

Completeness5/5

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

Despite 11 parameters and no output schema, the description covers the full creation workflow, safe execution pattern, SSL caveat, experimental warnings, and cross-references other tools. It is sufficiently complete for agent usage.

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

Parameters4/5

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

Schema coverage is 82% with per-parameter descriptions. The description adds operational semantics like dry_run/confirm pattern, php_handler preference via site_get, and experimental nature of new_owner, which go beyond the schema.

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 it creates a new website in FastPanel via the wizard endpoint, distinguishes from SSL tool, and specifies atomic creation of owner/database/FTP. Sibling tools like site_update and certificate_create_letsencrypt are differentiated.

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

Usage Guidelines5/5

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

Explicitly instructs to use dry_run:true first, then confirm:true for safe execution. Recommends calling certificate_create_letsencrypt after site is active. Provides the two-step API flow, making usage clear.

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/iMateo/fastpanel-mcp'

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