Skip to main content
Glama
iMateo

fastpanel-mcp

by iMateo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

site_configuration_update

DestructiveIdempotent

Update nginx, Apache, and PHP config for a site. Auto-validates with nginx -t and reverts on failure when SSH is configured. Supports partial updates by fetching current values for omitted blocks.

Instructions

Replace the nginx (frontend), apache (backend) and php.ini config for a site. DANGEROUS: invalid syntax can take down the site or the whole nginx/apache service. SAFETY NET: when SSH is configured (FASTPANEL_SSH_HOST) and validate:true (the default), the tool runs nginx -t right after applying and AUTO-REVERTS to the previous config if it fails, so a bad edit can't leave nginx unable to reload. Without SSH there is NO validation — preview with dry_run and double-check by hand. ⚠️ SIDE EFFECT — manual mode: the first config update flips the site to manual_changes=true on the panel side. After that, FastPanel STOPS managing this site's config: it will no longer auto-insert the 443 server block, the HTTP→HTTPS redirect, or Let's Encrypt renewal/acme-challenge locations when you issue or renew SSL. You become responsible for the full HTTPS block (including ssl_certificate paths — get them from certificates_list crt_path/key_path). Partial update IS supported here (unlike the raw API): omit any of frontend/backend/phpini and the tool fetches the current value via site_configuration_get and sends it back unchanged, so you can safely change just one block. Endpoint: PUT /api/sites/{site_id}/configuration. WRITE — confirm:true required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phpiniNoFull php.ini overrides for this site. Omit to keep current.
backendNoFull apache/httpd config for this site (VirtualHost block). Omit to keep current.
confirmNo
dry_runNo
site_idYesSite id from sites_list
frontendNoFull nginx config for this site (HTTPS server block + HTTP redirect block). Omit to keep current.
validateNoWhen SSH is configured (FASTPANEL_SSH_HOST), run `nginx -t` right after applying and AUTO-REVERT to the previous config if it fails. Set false to skip the check (no effect if SSH is unconfigured — there is no validation either way then).

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

The description discloses far beyond annotations: safety net with validation and auto-revert, side effect of manual mode, partial update behavior. Annotations (destructiveHint=true, idempotentHint=true) are consistent and the description adds crucial context.

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?

The description is front-loaded with the main action, uses structured warnings and bullet-like formatting. It is slightly long but every sentence is informative; could be tightened slightly.

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?

For a high-risk write operation, the description covers safety net, side effects, partial updates, endpoint, and references to related tools. No output schema, but the behavioral info is comprehensive.

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 71% high, but description adds value: explains that omitting a param keeps current, the validate param behavior, and the SSH prerequisite. This goes beyond the schema's descriptions.

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 tool replaces nginx, apache, and php.ini config for a site. It distinguishes from siblings like site_configuration_get (read) and site_backend_update (partial) by explaining partial update support and the full scope.

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?

Guidelines are strong: it explains when to use (replace config), warns about danger, and contrasts with raw API. However, it does not explicitly say when NOT to use, e.g., if only backend update is needed, there is site_backend_update sibling.

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