Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_web_server_config_generator

Read-onlyIdempotent

Generates Apache 2.4, nginx, and Caddy 2 configuration files from a single structured input, including TLS, reverse proxy, PHP-FPM, static file serving, security headers, and logging.

Instructions

Apache / Nginx / Caddy Web Server Config Generator. Build ready-to-deploy web server configuration text for Apache 2.4, nginx, and Caddy 2 from one structured input. A single request returns all three parallel outputs (Apache VirtualHost, nginx server block, Caddyfile) covering TLS with optional HTTP-to-HTTPS redirect and HSTS, reverse proxy with WebSocket upgrade, PHP-FPM FastCGI dispatch, static-file serving with cache expiry, gzip, security headers, custom error pages, and access/error logging. It only BUILDS config text from your parameters; it never writes files to disk, edits a live server, reloads, or restarts anything. Use this for full virtual-host or server-block files; use linux_htaccess_generator for an Apache per-directory .htaccess instead, or linux_ssh_config_generator for SSH client/daemon config. Set operation to generate (the default, requires serverName) or to presets to list curated starter configurations. Runs locally on the values you provide, read-only and non-destructive, contacts no e

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoMode: generate builds the config text (requires serverName); presets returns the curated starter list and ignores all other fields.generate
serverNameNoPrimary hostname for the virtual host or server block (for example example.com). Required when operation is generate; max 253 chars; underscore is accepted as the nginx default-server placeholder.
serverAliasesNoExtra hostnames (ServerAlias / additional server_name entries). Blank entries are dropped.
httpPortNoPlain-HTTP listen port.
httpsPortNoHTTPS listen port (used only when ssl.enabled is true).
documentRootNoFilesystem path served as the web root (DocumentRoot / root)./var/www/html
gzipNoEmit gzip / compression directives for text responses.
sslNoTLS settings.
reverseProxyNoReverse-proxy / upstream settings.
phpNoPHP-FPM FastCGI settings.
staticNoStatic-file serving settings.
securityNoSecurity-header and server-token settings.
errorPagesNoMap of HTTP status code (as key) to a custom error-page path.
loggingNoAccess / error log settings.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
operationNoThe operation performed (generate or presets).
resultNoFor generate: the three configs plus warnings and explanation. For presets: a presets array of starter configurations.
Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description reinforces by stating the tool 'only BUILDS config text' and 'never writes files, edits a live server, reloads, or restarts anything.' This adds meaningful context beyond annotations, though it could mention more about idempotency.

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 purpose and provides a comprehensive overview. It could be slightly more concise, but the structure is logical and covers capabilities, constraints, and alternatives without excessive verbosity.

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 tool's complexity (14 parameters, nested objects, output schema), the description covers all major features (TLS, reverse proxy, PHP, static, security headers, error pages, logging) and the two modes. The output schema exists, so return values are not required. It feels complete for the context.

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%, so the description does not need to explain parameters extensively. It mentions a few key constraints (requires serverName for generate) but does not add significant new meaning beyond what is already in the input 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 generates configuration text for Apache, Nginx, and Caddy web servers. It specifies the exact output (VirtualHost, server block, Caddyfile) and explicitly distinguishes from sibling tools like linux_htaccess_generator and linux_ssh_config_generator.

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?

The description provides explicit guidance on when to use this tool (for full virtual-host or server-block files) and when to use alternatives (linux_htaccess_generator for .htaccess, linux_ssh_config_generator for SSH config). It also explains the two modes (generate and presets) and prerequisites.

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/Jambozx/onlinecybertools-mcp-server'

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