wisp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WISP_API_TOKEN | Yes | Your WISP Client API token | |
| WISP_PANEL_URL | Yes | The URL of the WISP panel (e.g., https://panel.example.com) | |
| WISP_SERVER_ID | No | Optional default server ID | |
| WISP_ALLOW_POWER | No | Set to 'true' to allow power operations (start, stop, restart) | |
| WISP_ALLOW_BACKUPS | No | Set to 'true' to allow backup operations | |
| WISP_ALLOW_COMMANDS | No | Set to 'true' to allow sending console commands | |
| WISP_ALLOW_DATABASES | No | Set to 'true' to allow database operations | |
| WISP_ALLOW_DESTRUCTIVE | No | Set to 'true' to allow destructive operations (file deletion, backup restore/delete, database deletion, force-kill, panel update). Keep false during normal administration. | |
| WISP_ALLOW_FILE_WRITES | No | Set to 'true' to allow file write operations | |
| WISP_ALLOW_SERVER_SETTINGS | No | Set to 'true' to allow modifying server settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capabilitiesA | Show the configured server and enabled operation classes. Never returns secrets. |
| list_serversB | List one page of servers. include may contain node, egg, or allocations. |
| server_detailsB | Get server metadata. include may contain node, egg, allocations, or features. |
| server_statusB | Get power state, CPU, RAM, disk, network, and game-query information. |
| audit_logsB | Read paginated server audit logs. |
| list_directoryA | List one page of a server directory. Use page/per_page for large directories. |
| read_fileB | Read a text file. Large files are truncated to protect model context. |
| file_fingerprintA | Return SHA-256 and size metadata for a text file without returning its content. |
| read_file_chunkA | Read a bounded character range from a text file with continuation metadata. |
| find_in_fileA | Find literal text in a file and return small line-numbered excerpts instead of the whole file. |
| read_log_tailA | Read the last N lines of a text log file. |
| create_directoryB | Create a directory. Requires file-write access. |
| write_fileC | Create or overwrite a text file. Requires file-write access. |
| safe_write_fileA | Overwrite an existing text file only if its SHA-256 still matches the value previously read. |
| replace_in_fileA | Replace an exact snippet server-side with optimistic concurrency, avoiding whole-file model output. |
| copy_fileC | Copy a file in place. Requires file-write access. |
| rename_fileA | Rename or move a file. Requires file-write access. |
| compress_filesC | Compress server files. Requires file-write access. |
| decompress_archiveC | Decompress an archive. Requires file-write access. |
| delete_fileC | Delete a file. Requires file-write and destructive access. |
| send_console_commandB | Send one server-console command. Requires command access. |
| powerA | Start, stop, restart, or force-kill a server. Kill also requires destructive access. |
| list_backupsB | List one page of server backups. |
| create_backupB | Create a server backup. Requires backup access. |
| deploy_backupC | Restore a backup. Requires backup and destructive access. |
| delete_backupA | Delete a backup. Requires backup and destructive access. |
| lock_backupA | Lock a backup against accidental deletion. Requires backup access. |
| backup_downloadC | Request the panel's download response for a backup. |
| list_databasesA | List one page of databases attached to a server. |
| create_databaseC | Create a database when the panel supports the Wisp Client API endpoint. |
| rotate_database_passwordB | Rotate a database password. Requires database and destructive access. |
| delete_databaseB | Delete a database. Requires database and destructive access. |
| toggle_monitoringC | Toggle Wisp server monitoring. Requires server-settings access. |
| toggle_support_accessC | Toggle provider support access. Requires server-settings access. |
| update_serverB | Run the Wisp egg update action. Requires server-settings and destructive access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 35 tools
Every tool targets a distinct operation or resource: file reads/writes/deletes, backups, databases, power, console, settings, etc. Even closely related file tools (read_file, read_file_chunk, read_log_tail, find_in_file) have clearly different purposes, so an agent can reliably select the right one.
Most tools follow a clear verb_noun pattern (e.g., list_servers, create_backup, delete_file). A few nouns stand alone (capabilities, server_details, server_status, audit_logs, file_fingerprint, backup_download), which is a minor but noticeable deviation from the predominant style.
With 35 tools, the set is well beyond the 25+ threshold and feels heavy. While the server covers multiple domains (files, backups, databases, console, settings), the sheer number of tools makes it more complex to navigate than a typical MCP server, and many could be consolidated or exposed via subcommands.
The tool surface is comprehensive for server management: CRUD for files, backups, databases, plus power, console, monitoring, and settings. A few gaps exist (no server creation/deletion, no user/permission management), but these are likely outside the intended read-only or operational scope.